Im wondering if it is possible to interconnect multiple crossbar
routers, with embedded components.
Not yet (today): router-to-router communication / federation is a feature high on our prio list. It'll be there. Can't give you a date though.
When it's there, you'll be able to have your app components also distributed transparently over routers.
Here is what I want to acomplish:
A central router, with a python component and web frontend (worldwide
visible). And various small routers with python components (and
medium/high cpu load), wich can (and should) work offline, also, they
shoul be monitored/confiugred in real time from local lan, and when
internet connection is available, they connect with the central router
to upload their work, ask for more work, and inform their progress.
When a router looses it's connections to peer routers (in a federated/clustered network of routers), then all remote procedures available only via other routers will simply "disappear" on the local router. Also, any event published via that local router won't be forwarded to other routers (obvisously). And those events won't be "replayed" to remote routers once the uplinks become available again.
What looks desirable is to have means for applications to hook into the process of establishing / loosing a router uplink. E.g. events
Application components might then subscribe to those events and perform necessary work like "upload their work" etc
I have added an issue to track this:
Is there a way to configure an ApplicationSession to interact with two
routers? or what should be the best approach to implement this?
A given WAMP session is alway connected to a specific router, and attached to a specific realm on that router.
Hence, to talk to 2 routers, you need 2 ApplicationSession's.
Am 20.06.2014 09:03, schrieb DeJhanX:
You received this message because you are subscribed to the Google
Groups "Autobahn" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to autobahnws+...@googlegroups.com
For more options, visit https://groups.google.com/d/optout.