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
In Wiola, today, dynamic authentication should be implemented in Lua and runs as part of Wiola/Openresty.
This makes it hard to swap router implementations.
Particularly, in crossbar.io, authenticators are just another RPC callees, therefore if there was another router supporting the same paradigm (Wiola? :), it could've been used as a drop in replacement without re-implementing authenticators.
I understand that Dynamic Authentication is not defined in WAMP spec and thus every router is free to implement it any way it likes, but crossbar.io is de-factor the reference implementation, so may be it's worth to align with it for the sake of interoperability.
What do you think?
The text was updated successfully, but these errors were encountered:
30 авг. 2018 г., в 11:59, Zaar Hai ***@***.***> написал(а):
In Wiola, today, dynamic authentication should be implemented in Lua and runs as part of Wiola/Openresty.
This makes it hard to swap router implementations.
Particularly, in crossbar.io, authenticators are just another RPC callees, therefore if there was another router supporting the same paradigm (Wiola? :), it could've been used as a drop in replacement without re-implementing authenticators.
I understand that Dynamic Authentication is not defined in WAMP spec and thus every router is free to implement it any way it likes, but crossbar.io is de-factor the reference implementation, so may be it's worth to align with it for the sake of interoperability.
What do you think?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
In Wiola, today, dynamic authentication should be implemented in Lua and runs as part of Wiola/Openresty.
This makes it hard to swap router implementations.
Particularly, in crossbar.io, authenticators are just another RPC callees, therefore if there was another router supporting the same paradigm (Wiola? :), it could've been used as a drop in replacement without re-implementing authenticators.
I understand that Dynamic Authentication is not defined in WAMP spec and thus every router is free to implement it any way it likes, but crossbar.io is de-factor the reference implementation, so may be it's worth to align with it for the sake of interoperability.
What do you think?
The text was updated successfully, but these errors were encountered: