summaryrefslogtreecommitdiff
path: root/examples/chat/README
diff options
context:
space:
mode:
authorMartin Sustrik <sustrik@250bpm.com>2010-02-24 09:17:05 +0100
committerMartin Sustrik <sustrik@250bpm.com>2010-02-24 09:17:05 +0100
commitccd47f1ee8c9268b99478c6cce3d8b1aada62566 (patch)
tree680e9b474e22321ab0401bc899b90b31e463c4da /examples/chat/README
parent8980a985828579d03f031b18a1bebcd65eded417 (diff)
chat example moved to separate repo
Diffstat (limited to 'examples/chat/README')
-rw-r--r--examples/chat/README42
1 files changed, 0 insertions, 42 deletions
diff --git a/examples/chat/README b/examples/chat/README
deleted file mode 100644
index b93aefd..0000000
--- a/examples/chat/README
+++ /dev/null
@@ -1,42 +0,0 @@
-
-This example is a simple instant messaging implementation. There are multiple
-participants in the chat, both sending and reading messages. The sending
-application 'prompt' is separated from the application displaying the chat
-'display' so that there's no need for sophisticated GUI.
-
-To run the example you'll need both applications plus the 'forwarder' device
-that will play role of messaging server (chatroom). Build it this way:
-
-$ ./autogen.sh
-$ ./configure --with-chat --with-forwarder
-$ make
-$ sudo make install
-
-Once it is built create the configuration file (say config.xml) for the
-forwarder describing which network endpoints are to be used for incoming and
-outgoing messages:
-
-<forwarder>
- <in>
- <bind addr = "tcp://eth0:5555"/>
- </in>
- <out>
- <bind addr = "tcp://eth0:5556"/>
- </out>
-</forwarder>
-
-You are of course free to define mutliple endpoints for either incoming or
-outgoing messages.
-
-Now start the forwarder:
-
-$ zmq_forwarder ./config.xml
-
-At this point the messaging server is ready to accept connections from
-messaging clients. When starting the sending application, specify your name
-so that messages can be attributed to you:
-
-$ ./prompt tcp://myserver:5555 "John Doe"
-
-$ ./display tcp://myserver:5556
-