I am working on architecture (still) to move to a newer version of AB. I
am still trying to understand some of the basic concepts. Like the
Since you've been using this stuff for a longer time and still don't feel confident understanding the concepts, I'd call that our fault;(
I really want to improve on this. My problem is: how can we make it easier to understand? What is missing?
When you look at these two resources
do you have a hint which one is more approachable for you? Then we can work from there and improve. Or any other hints?
dealer which connects an rpc caller to the rpc call itself. I think I
get that. So, I could have a web page->dealer->dbquery (for example)
Yep. The complete picture looks like this
Web Page <-- WAMP --> Dealer <-- WAMP --> Backend Component <-- SQL --> Database
rpc call from the web page through the dealer to the dbquery rpc. I like
that architecture, except that the dealer is always involved. I wonder
"Dealer is always involved": That is by design. It is _necessary_ to achieve the goal of decoupling. If you kick out the Dealer, then the Caller would need knowledge of where and how to reach the Callee. Which means, both would be coupled.
Why are you concerned about "Dealer is always involved"?
if there is a way to bypass that dealer, (or all dealers). For example,
once my web page->dealer->dbquery is done the first time, I could have
an rpc call that returns the 'address' of the dbquery, so that
The "address" of a Callee is exactly what we do _not_ want to have the Caller know about.
subsequent queries could effectively do web page->dbquery. Or for that
No. Not possible.
matter, could I have two paths to a dbquery rpc, like a second route
from web page-> other dealer->dbquery. The only thing different in
this chain is a 'other dealer'. In these examples 3 routes are
considered from a web page ----- X ----> dbquery. Is it possible to
have multiple routes to the same endpoint?
Not sure I get what you mean. Multiple routes to the same endpoint will be a common situation with _clustered_ routers:
Caller1 ---> Dealer1 ---> Callee1
Caller2 ---> Dealer2
Here, Dealer1 and Dealer2 together form a "clustered WAMP router".
Caller1 and Caller2 in above are connected to different Dealers, whereas Callee1 is only connected to Dealer1.
That means, to have Caller2 call into Callee1 requires routing of the call from Dealer2 to Dealer1 and then to Callee1.
Hopefully above does not confuse you futher;)
Am 08.08.2014 06:08, schrieb Greg Fausak:
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
To post to this group, send email to autob...@googlegroups.com
To view this discussion on the web visit
For more options, visit https://groups.google.com/d/optout.