You do not have permission to delete messages in this group
Copy link
Report message
Sign in to report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to autob...@googlegroups.com
hi,
is routing between realms on the same crossbar router possible?
we have a front-end talking to frontend clients, and a backend with a database.
it would be good to have a public realm and a private realm, with the frontend methods acting as a proxy for backend calls.
regards
ralph
Tobias Oberstein
unread,
May 27, 2015, 6:19:26 PM5/27/15
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Sign in to report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to autob...@googlegroups.com
Am 25.05.2015 um 06:20 schrieb ralph stone:
> hi,
>
> is routing between realms on the same crossbar router possible?
No. Realms are fully separated by design.
> we have a front-end talking to frontend clients, and a backend with a
> database.
> it would be good to have a public realm and a private realm, with the
> frontend methods acting as a proxy for backend calls.
WAMP has auth. roles which you can use to restrict the set of procedures
visible/accessible to some client - frontend or backend.
You do not have permission to delete messages in this group
Copy link
Report message
Sign in to report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to autob...@googlegroups.com
You could have backend clients that connect to both realms, which would act as a sort of bridge.
Web UI --> Public
Realm <---------\
| | Router Remote facade component
| |
Private <---------/
Realm <------------- Database component
This has the advantage of making critical backend components less exposed to peers on the publicly-accessible realm. I'm actually planning on using this approach in my work project. I haven't implemented it yet, so I cannot tell you how well this works.