On Mon, Oct 13, 2008 at 2:18 PM, Simon Laws <[EMAIL PROTECTED]>wrote:
> > > On Mon, Oct 13, 2008 at 2:10 PM, ant elder <[EMAIL PROTECTED]> wrote: > >> >> >> On Mon, Oct 13, 2008 at 2:08 AM, Raymond Feng <[EMAIL PROTECTED]>wrote: >> >>> I'm wondering if we can combine the Endpoint and RRB efforts together. >>> Here are some ideas: >>> >>> 1) An SCA service has a list of Endpoints representing the end point for >>> each binding protocol. >>> >>> 2) An SCA reference has 0..N Endpoints depending on the multiplicity of >>> the reference. >>> >>> 3) Each endpoint has a binding interface contract. If it's not known >>> before the operation selector, then it's an "Any" interface with an "Any" >>> operation. >>> >>> 4) There is one invocation chain for each endpoint (based on the binding >>> interface contract) and one for the SCA service or reference. The two >>> invocation chains are connected as we described on the wiki page. For a SCA >>> service configured with multiple bindings, there will be multiple endpoint >>> invocation chains connecting to the same service invocation chain. It's >>> similar for SCA references. >>> >>> Thanks, >>> Raymond >>> >>> >> From all the discussion I know what the RRB is but are there any emails or >> doc you could point to saying what the endpoint effort is about? Or if there >> are not yet could you give a quick summary? >> >> ...ant >> >> > Hi Ant > > Touche, you got this mail precisely the same time as I did:-) We talked > about extending the endoint support a while back (It's on the roadmap page > [1]) and it was discussed on the ML back in June [2]. Sebastien subsequently > raised a JIRA and referenced the mail list [3]. I think it's a good idea to > bring this up again now as it is related to the RRB work. > > Simon > > [1] > http://cwiki.apache.org/confluence/display/TUSCANYWIKI/Roadmap+Discussion > [2] http://marc.info/?l=tuscany-dev&m=121318046912690&w=2 > [3] http://issues.apache.org/jira/browse/TUSCANY-2382 > And I managed to reply to your mail without giving a summary of what one of the Endpoints we are talking about is. It's basically the result of combining a reference with a binding or a service with a binding. It describes the physical Endpoint (for want of a better word) that produces or consumes messages. Originally instigated to straighten out the binding/reference multiplicity confusion but could be applied to services also. Needs reviewing now in light of the RRB discussion, mainly because wires also have endpoints but they are slightly different. Hope that helps. Simon
