On Thu, Apr 21, 2011 at 9:09 AM, ant elder <[email protected]> wrote: > On Wed, Apr 20, 2011 at 3:28 PM, Simon Laws <[email protected]> wrote: >>> >>> What is it needed for? If its just for tests to set the http port to >>> default to 8085 instead of 8080 then there is a static field on the >>> http server class which tests can set. >>> >>> ...ant >>> >> >> So here's a scenario. One the same machine start two Tuscany nodes to >> run two composites from the same domain that have components that talk >> to each other over the default binding remoted using web services. >> > > I can't see why that scenario shouldn't work ok with whats there now. > Anyway, like i said earlier i didn't implement anything for the base > URIs but it shouldn't be hard to do. It doesn't seem like the best > approach to me though and i don't remember any scenarios being given > in the past that explained why its necessary. > > ...ant >
I think we first need to agree (or not) whether we need to be able to set HTTP port numbers. Only then can we establish what a suitable mechanism is. Otherwise the two points become confused. Based on previous (and current based on the "Allow the lookup of endpoint address by component/service/binding name from the Node API" thread) experience I'm first asserting that we need to be able to set HTTP port numbers in order that the user of the runtime is able to set values other than the defaults chosen by Tuscany. I'm not saying how these values should be set by the user. Simon -- Apache Tuscany committer: tuscany.apache.org Co-author of a book about Tuscany and SCA: tuscanyinaction.com
