Bug278 Editing
Somebody reported #fresco that he needs to run the omniorb nameserver for the hello world example while all the other demos were updated not to rely on the nameservice anymore. This was rather surprising for him. We should update the example in the tutorial to the new server resolution code.
> Somebody reported #fresco that he needs to run the > omniorb nameserver for the hello world example > while all the other demos were updated not to rely > on the nameservice anymore. This was rather > surprising for him. > > We should update the example in the tutorial to > the new server resolution code. oh well. The goal of the tutorial was/is to explain fresco. For that, I'd like the concepts to be simple. While with the 'new server resolution' chances to get it running are slightly better, it's conceptually quite a bit more involved. Yes, you could say 'it's just a server lookup', but I was fond of it being a 'standard way', i.e. not our domain. Now we have to explain (justify, maintain, etc. etc.) that, too. I agree that the tutorial should be updated. And I'm reminded that I don't like the current server lookup code at all. Even less than what we had before.
*cough* What, you say the new server resolution stuff is too complicated? *cough* Who knew? *cough* ;-)
erm, I never said the contrary ;-)
We should at least clearly document that the server resolution works differently from the one used in the demos.
GLGIDm <a href="http://wtsgzxehzbty.com/">wtsgzxehzbty</a>, [url=http://zgnadxprwegn.com/]zgnadxprwegn[/url], [link=http://bpkasugvttrq.com/]bpkasugvttrq[/link], http://nnhufuylhfyk.com/
not logged in
register
Home