Re: gdomap problem

[Richard Frith-Macdonald]

On 2005-09-12 19:52:33 +0100 Richard Frith-Macdonald 
<richard@brainstorm.co.uk> wrote:

> On 2005-09-12 14:55:44 +0100 Chris Vetter <cbv@gmx.net> wrote:
>
> > One more problem...
> >
> >     chuck:root :0> gdomap -N
> >     No names currently registered with gdomap
> >     chuck:root :0> gdomap -L GNUstepGSPasteboardServer
> >     Unable to find GNUstepGSPasteboardServer.
> >     chuck:root :0> gdomap -L GDNCServer
> >     Unable to find GDNCServer.
> >
> > Well, yes, gdomap did tell me that no names are registered, however, gdnc
> > and gpbs ARE running:
>
> No problem then ... most likely you didn't read the release notes about 
> gpbs 
> and gdnc now being private (using unix domain sockets) by default.

Oops ... I sent that incomplete email by accident ... I meant to look up 
where these changes are documented, and explain in more detail, but the gist 
of it is ...

NSConnection *default* behavior is changing to be like MacOS-X (connections 
private to the user and local to the host) rather than like NeXTstep 
(connections publicly usable across the LAN).

Private connections use NSMessagePort rather than NSSocketPort (implemented 
using unix domain sockets) and their names are handled by entries in the 
local filesystem accessible only to the owning user account ... so they 
don't appear in gdomap (which deals with names of connections used for 
network connections which can be used to communicate between different users 
and different machines).

So ... you should not expect to see gpbs and gdnc registered with gdomap by 
default now ... unless you are running windows ... since windows does not 
have unix domain sockets, and therefore does not have private 
(NSMessagePort) connections.