Allow multiple RPC interfaces to be registered across multiple backends

iTwin / viewer

Monorepo that contains the iTwin Viewer npm packages and their related packages

MIT License

25 stars 16 forks source link

Allow multiple RPC interfaces to be registered across multiple backends #247

Closed ben-polinsky closed 1 year ago

ben-polinsky commented 1 year ago

The current API today is mostly centered around registering a single backend for use by all of the RPCs that would be registered to the iModelApp.

We need to update that to start thinking about how we let people register an RPC, or group of RPCs, with a specific backend url and allow multiple to be configured

aruniverse commented 1 year ago

fyi @swbsi , we'll work on it but just wanted to keep you in the loop and get your opinions/advice

swbsi commented 1 year ago

Sounds good.

FYI, the RPC system internally should have no problem supporting this.

Interfaces/impls are paired with a configuration, which fully defines things like which server to connect to.

ben-polinsky commented 1 year ago

PR: https://github.com/iTwin/viewer/pull/236