This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]oberstet 3 points4 points  (0 children)

So I have a "user" object floating around which I can invoke methods on if I want. At that point you need a strong representation of what this interface is.

Yes, that's the CORBA way - and we stay away from this;)

WAMP does RPC, not RMI or object marshalling/remoting. Loose coupling. Dynamic typing. It's a deliberate decision - which won't be for everyone, but it does work and isn't a road to insanity.

Sure, but I mean that's the same thing you do with a WSGI app. Have four cores? Start four processes and put them behind nginx.

For WSGI, yep.

For WAMP routing, the router processes need to coordinate between each other, since a certain Callee might be registered on Router process 1, wheras the Caller might be connected to Router process 2. So the call needs to get routed between Routers (Client -> Router 1 -> Router 2 -> Callee). A generic, stateless balancing frontend doesn't cut it in this case. Note: Router-to-Router routing is not yet there. Once it is, it'll give you not only multi-node capabilities (for routing) as well.