You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue proposes support for multiple protocols.
Allowing users to define multiple protocols would enable the following capabilities / benefits:
increased crossform capabilities by having different platforms use different protocols (eg web-specific components)
support for multiple versions of an application, this is especially useful if there are no automatic updating capabilities, enabling backwards compatibility
different protocols for different authorization levels (-> different security levels for different protocols)
ab testing / something like beta testing or similar
increases overall modularity
Regarding implementation:
using the existing protocol id, the client could choose which protocol to enable during handshake
Unresolved Pain-Points:
possibility for leafwing inputs to conflict (?)
possibility for authority to conflict (ie one protocol allows the user to control an entity while the other one only allows the server)
Overall this proposal obviously lacks refinement, so any feedback is appreciated :)
The text was updated successfully, but these errors were encountered:
This issue proposes support for multiple protocols.
Allowing users to define multiple protocols would enable the following capabilities / benefits:
Regarding implementation:
Unresolved Pain-Points:
Overall this proposal obviously lacks refinement, so any feedback is appreciated :)
The text was updated successfully, but these errors were encountered: