Skip to content
This repository


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

A dirt simple library for peer discovery and message passing between Ruby applications on a LAN.

branch: master

Fetching latest commit…


Cannot retrieve the latest commit at this time

Octocat-spinner-32 bin
Octocat-spinner-32 broken
Octocat-spinner-32 lib
Octocat-spinner-32 rdoc
Octocat-spinner-32 scripts
Octocat-spinner-32 test
Octocat-spinner-32 website
Octocat-spinner-32 .gitignore
Octocat-spinner-32 Gemfile
Octocat-spinner-32 Gemfile.lock
Octocat-spinner-32 HISTORY
Octocat-spinner-32 LICENSE
Octocat-spinner-32 License.txt
Octocat-spinner-32 README.rdoc
Octocat-spinner-32 Rakefile
Octocat-spinner-32 VERSION
Octocat-spinner-32 journeta.gemspec
Octocat-spinner-32 setup.rb



Journeta is a dirt simple peer discovery and message passing library for processes on the same LAN, requiring no advanced networking knowledge to use.

Only core Ruby libraries are required, making the library fairly light. As all data is sent across the wire in YAML form, any arbitrary Ruby object can be sent to peers, provided they..

* Are running a compatible Journeta version.
* Have access to the same class definitions if you are sending your own custom objects.
* Do not have a firewall preventing network I/O.

Journeta uses Ruby threading to manage the asynchronous nature of peer-to-peer I/O. Data you send from your application thread will be queued and sent asynrchonously as soon as possible. For insight into events internal to the library, start ruby with the `–debug` options.



   A completely distributed, zero-configuration-required chat room script.
   Fire up several instances in separate terminals. Multiple instances on the same machine is ok.
   Everything you type will automatically be sent to all other instances on the LAN!
   Use `ruby --debug journeta_instant_messenger.rb` for detailed internal event details.


Monitors the presence of all peers on the network.


A simple queue managed by a server. Each client produces jobs to be queued, and processes jobs sent from the server(s). All nodes automatically find eachother. Try running multiples clients, and then multiple servers. Notice that when you have N servers, each job gets run N times, and not necessarilly by the same client!


Preston Lee


How Journeta discovers peers using UDP multicasting..

Something went wrong with that request. Please try again.