# from Scott Gifford
# on Sunday 13 April 2008 19:14:
You can simplify both of these by providing a network client that
speaks a simple TCP-based protocol and relays messages to/from the IRC
server/multicast network/Jabber server.
Well, that's what I'm doing now -- sans the IRC relay. The
Eric Wilhelm [EMAIL PROTECTED] writes:
Hi all,
I'm trying to figure out whether this has been done before and/or
looking for suggestions on the best way to implement it.
I would like the publish clients to connect to a server, then publish
their message and disconnect. (Optionally, they
On Apr 14, 2008, at 02:41, Eric Wilhelm wrote:
# from Scott Gifford
# on Sunday 13 April 2008 19:14:
You can simplify both of these by providing a network client that
speaks a simple TCP-based protocol and relays messages to/from the
IRC
server/multicast network/Jabber server.
Well,
Hi all,
I'm trying to figure out whether this has been done before and/or
looking for suggestions on the best way to implement it.
I would like the publish clients to connect to a server, then publish
their message and disconnect. (Optionally, they can stay connected and
publish more
On Apr 11, 2008, at 9:23 PM, Eric Wilhelm wrote:
...
I would like the publish clients to connect to a server, then
publish
their message and disconnect. (Optionally, they can stay connected
and
publish more messages.)
The subscribe clients would hold persistent connections to the
server