Skip to content
Projects
Groups
Snippets
Help
Loading...
Sign in / Register
Toggle navigation
L
libzmq
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Packages
Packages
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
submodule
libzmq
Commits
c98e29fb
Commit
c98e29fb
authored
Dec 08, 2009
by
Martin Sustrik
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
README added to chat example
parent
902d4f22
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
42 additions
and
0 deletions
+42
-0
README
examples/chat/README
+42
-0
No files found.
examples/chat/README
0 → 100644
View file @
c98e29fb
This example is a simple instant messaging implementation. There are multiple
partipants in the chat, both sending and reading messages. The sending
application 'prompt' is separated from the application displayinf 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 build 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
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment