Hi,
Here is one way I got working locally:
1) Use tribes-based endpoint registry. To form a group, we use the same
multicast address (228.0.0.100) and port (50000). We also use the domain URI
as the name of the replicated map so that only nodes with the same domain
URI are in the same group.
2) For binding.sca service binding, I find a free TCP/IP port and construct
a http://<host>:<port>/<uri> so that binding.ws is listening on that URL on
behalf of binding.sca. Then the endpoint with such binding.sca is propagated
to the client node.
3) The client node looks up the remote endpoint from the EndpointRegistry.
It gets the physical binding URI and makes WS calls into the remote service
on behalf of binding.sca.
Thanks,
Raymond
--------------------------------------------------
From: "Simon Laws" <[email protected]>
Sent: Thursday, June 25, 2009 12:56 AM
To: <[email protected]>; <[email protected]>
Subject: Re: [2.x] remote binding.sca
[[snip]]
- Did you get any further in the thinking about decoupling binding.sca
from the hosting environment. Or to put it another way, what
technology and default configuration should we adopt?
Simon
