Re: gdomap and registered names

[Richard Frith-Macdonald]

On 28 Jun 2010, at 11:36, Quentin Mathé wrote:

> I don't really want to use this feature, I was just curious. I suppose 
> registering names with -R might be useful when you want to keep some names 
> reserved.

I suppose it might ... though I think I really had fixing accidental 
unregistration (and testing)  in mind.

> Looks like I was omitting the port number. However it still doesn't work if I 
> use (I checked that 538 is the port declared in /etc/services):
> sudo gdomap -P 538 -R Test

That's an attempt to register the name 'Test' for port 538 ... meaning that 
apps trying to make an NSSocketPort based connection to 'test' would connect to 
538.
Obviously that wouldn't work for them ... because there's no GNustep app 
listening for DO on that port, but the registration process ought to work.

> I get "failled to contact gdomap on myhostname(127.0.1.1) - Connection 
> refused". If I swap the argument order (sudo gdomap -R Test -P 538), I get a 
> different error:
> "attempted registration with bad port"

Are you sure it was that way round ... I would expect it to be the other way 
round.

If you do 'gdomap -R Test -P 538' you are telling it to first register 'Test' 
on port 0 and then use port 538 for the next registration ... so you should get 
a 'bad port' message because you can't register anything on port 0.  Actually I 
suppose it might be worth adding a check for the gdomap port too, since it 
makes no sense to register a name for that.

If you do 'gdomap -P 538 -R Test' you are telling it to register 'Test' on port 
538 and I would expect a connection refused message if the daemon is not 
running, but a success otherwise.