On Mon, 29 Aug 2005, Colin Western wrote:
>
> > > > In windows, it's relatively easy:
> > > > - Create a window handle with name appname_apphandle.
> > > > (can be reduced to simply appname if only one instance will be
> > > > running, see the thread about single instances for my suggestion
> > > > about that)
> > > > - Use this handle to send a message to with WM_COPY.
> > > >
> > > >
> > > > On linux/Unix:
> > > > - Create a unix socket /tmp/appname.appid under /tmp
> > > > or under ~/.appname/appid
> > > > (same remark about single instance)
> > > >
> > > > - Use this socket to send message to with standard socket
> > > > functions.
> > > >
> > > >
> I think that on Linux/unix you should use the X windows message passing, so
> that you can talk between programs running on different machines. I have had a
> stab at this in the past, and I attach a draft version. Though not shown in
> the attached, under MS windows I used RegisterWindowMessage('SpecialName');
> and looked for this specific message in the appropriate wndproc (or it could
> be the overall message loop)
This is only suitable for 2 processes running on the same desktop:
It is not suitable for a daemon; you cannot expect X to be present.
I have servers without X installed.
It also means you cannot connect to a process which is running as another
user on a different desktop, e.g. a VNC client.
Michael.
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
