On Jan 4, 2008 3:18 PM, ant elder <[EMAIL PROTECTED]> wrote: > On Jan 4, 2008 3:02 PM, Simon Nash <[EMAIL PROTECTED]> wrote: > > > Comments inline. > > > > Simon > > > > ant elder wrote: > > > On Dec 13, 2007 5:22 PM, Jean-Sebastien Delfino <[EMAIL PROTECTED]> > > > wrote: > > > > > (cut) > > >> > > >>I thought that the scenarios I described earlier helped describe the > > >>problem, which boils down to: > > >>domain != node > > >>so domain URI != node URI > > >>trying to make them equal is just wrong, and will break as soon as > > >>there's 2 nodes in a domain. > > >> > > > > > > > > > Ok but in the non-distributed case with just a single standalone node > > then > > > domain is the same as node isn't it, so domain uri could be the same > as > > node > > > uri? > > > > > Yes, I think it would be the same in this case. But this case is not > > very "interesting" in the broader scheme of things. And to make special > > use of the domain URI for this case only seems wrong to me. > > > > Its the way just about all the users posting to the user list seem to be > using Tuscany and its the way about 99% of the Tuscany samples and tests > run! That makes it at least a little bit interesting doesn't it ;-) Also, > if > we do whats below then its not really making a special case for this > standalone case. > > > > > The specs don't mention nodes, maybe what we need is to do 1.7.2 for > > nodes > > > and have a node base URI, i think that at least would help with all > the > > WS > > > endpoint problems we keep getting. > > > > > This seems a more useful path to follow. I'd like to understand in more > > > detail what you have in mind. Would services (potentially) be exposed > on > > two different endpoints (aliases), one with a node URI and another with > a > > domain URI? > > > > Have to admit I'm still struggling to understand how the domain and > multiple > nodes is really supposed to be working so not sure i can answer that yet. > Don't we have that issue today whether or not nodes have an explicit base > uri? > > ...ant
Reading back through this mail it seems that we are discussing two, potentially related, things. A. How we form URLs for the services that an SCA application exposes B. What do we do with the base domain URI scheme as described in the specification. There are many complexities in A spread around the specs. We have made several starts at trying to document the algorithm [1][2][3]. So can we discuss A without discussing B? Section 1.7.2 doesn't talk about a "domain URI" but does talk about a "base domain URI for a scheme". The spec describes only one of these for each scheme used in the SCA domain. This implies to me that either the base domain URI for a scheme: cannot be used as the base of the URI for the physical service URI as that will differ from node to node. It probably means it should provide a virtual set of endpoints for services in a similar way that a gateway/proxy would provide access to an organizations services at some externally recognizable endpoints. I think this is Sebastien's scenario2 OR is used in some way TBD to form the base URI that each service is exposed at. This is is Sebastien's scenario1 I think. Maybe the TBD is just to specify it on a node by node basis and take the spec with a pinch of salt. I don't think any of this differs based on the number of nodes we have (I am considering here that a single node is a domain with one node in it). To put it another way. It's complicated enough already so I would like it not to matter. Another issue that's bugging me is where these URI are calculated. The logic is spread around the code and currently depends on activating an assembly model. How about we develop an algorithm that is independent of binding activation that the bindings can contribute to so that the domain can know what the URIs will be without having to start each assembly. Simon [1] http://cwiki.apache.org/confluence/display/TUSCANYWIKI/Multiple+bindings+and+reference+multiplicity [2] Ant started a page somewhere but I can't find it now [3] http://cwiki.apache.org/confluence/display/TUSCANYWIKI/Binding+URI+Construction
