Page MenuHomePhabricator

Make ConduitCall always local/in-process
ClosedPublic

Authored by epriestley on Dec 10 2014, 6:16 PM.
Tags
None
Referenced Files
F15529108: D10959.id26325.diff
Tue, Apr 22, 4:49 PM
F15514300: D10959.id26314.diff
Fri, Apr 18, 1:36 AM
F15513519: D10959.id26315.diff
Thu, Apr 17, 7:28 PM
F15512914: D10959.id.diff
Thu, Apr 17, 2:52 PM
F15511548: D10959.diff
Thu, Apr 17, 2:55 AM
F15509904: D10959.diff
Wed, Apr 16, 5:21 PM
F15509143: D10959.diff
Wed, Apr 16, 10:02 AM
F15430902: D10959.id26315.diff
Mar 24 2025, 9:32 AM
Subscribers

Details

Summary

Ref T2783. ConduitCall currently has logic to pick a random remote server, but this is ultimately not appropriate: we always want to send requests to a specific server. For example, we want to send repository requests to a server which has that repository locally. The repository tier is not homogenous, so we can't do this below the call level.

Make ConduitCall always-local; logic above it will select ConduitCall for an in-process request or do service selection for an off-host request via ConduitClient.

Test Plan
  • Browsed some pages using ConduitCall, everything worked.
  • Grepped for removed stuff.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

epriestley retitled this revision from to Make ConduitCall always local/in-process.
epriestley updated this object.
epriestley edited the test plan for this revision. (Show Details)
epriestley added a reviewer: btrahan.
  • Found more stuff to remove.
btrahan edited edge metadata.
This revision is now accepted and ready to land.Dec 10 2014, 9:29 PM
This revision was automatically updated to reflect the committed changes.