Michael Van Canneyt wrote:
On Mon, 29 Aug 2005, Colin Western wrote:
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 indeed only suitable for two processes using the same X server,
but on the other hand the X system
is the only way you can guarantee that such processes can talk to each
other because that is the only thing you know they have in common. If
the programs are running on different machines then no other connection
may be possible.
It is not suitable for a daemon; you cannot expect X to be present.
I have servers without X installed.
Indeed - I was assuming this was for the LCL which assumes a display of
some sort (given that message loops were being discussed). Something
like sockets sounds the right idea here.
It also means you cannot connect to a process which is running as another
user on a different desktop, e.g. a VNC client.
Also true, though in this case you would have to explictly specify the
remote host as part of the connection.
I think we have two slightly different applictions in mind - Would
something like the Indy stuff be right for your daemons?
Colin
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
