Am 11.09.2014 21:40, schrieb Scott Wittenburg:
> Hi All,
>
> As I re-read this post, I don't think I made it clear that the two
> ApplicationSessions are probably nearly identical in the rpc methods
> they publish, so that without registering under different paths, the
> router could probably not know which one to pick.
Hi Scott,
a router does not care about which transport a component connects. This
is by design: a router can run multiple transports, and the WAMP level
does not (and should not) know about the specifics of a certain
transport (like for WebSocket, the fully qualified URL the client was
connecting to).
What you can do is prefix the WAMP URIs being registered for procedures
by a component, and then instantiate the component multiple times:
Component instance 1 (for user 123):
com.myapp.user.123.proc1
com.myapp.user.123.proc2
Component instance 2 (for user 456):
com.myapp.user.456.proc1
com.myapp.user.456.proc2
What is missing is dynamically firing up a component when a user connects.
Who/what is (should be) triggering the firing up of a component?
The user frontend session?
Or should the backend component already run when the user connects? In
which case, what else is the trigger?
> <mailto:autobahnws+unsub...@googlegroups.com>.
When using decorators, procedures are registered statically with respect to source code. However, when using register(), you are not limited in that way and can register (and unregister) completely dynamically ..
Sent from Mobile (Google Nexus 5)
To unsubscribe from this group and stop receiving emails from it, send an email to autobahnws+...@googlegroups.com.
To post to this group, send email to autob...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/autobahnws/1a8c5357-1294-48d6-abd5-a7e68127b90e%40googlegroups.com.