What’s this?

Arpie is a end-to-end framework for sending protocol-encoded messages over arbitary IO channels, including UNIX/TCP Sockets, Pipes, and pidgeon carriers (depending on your implementation details).

Arpie also provides a robust replay-protected RPC framework.

The useful core of arpie is a protocol stack that can be used to read/split/assemble/write any data stream, but is tailored for packeted streaming data.

The Arpie server uses one ruby-thread per client, the client runs entirely in the calling thread; though an example implementation for evented callbacks is provided.

Source Code

Source code is in git.

You can contact me via email at elven@swordcoast.net.

arpie is available on the rubygems gem server - just do gem1.8 install arpie to get the newest version.

Simple, contrived example: A string reverse server

require 'rubygems'
require 'arpie'
require 'socket'

server = TCPServer.new(51210)

e = Arpie::Server.new(Arpie::MarshalProtocol.new, Arpie::SizedProtocol.new)

e.handle do |server, ep, msg|
  ep.write_message msg.reverse
end

e.accept do
  server.accept
end

c = Arpie::Client.new(Arpie::MarshalProtocol.new, Arpie::SizedProtocol.new)
c.connect do
  TCPSocket.new("127.0.0.1", 51210)
end

c.write_message "hi"
puts c.read_message
# => "ih"

Advanced, but still simple example: Using Proxy to access remote objects

require 'rubygems'
require 'arpie'
require 'socket'

class MyHandler
  def reverse str
    str.reverse
  end
end

server = TCPServer.new(51210)

e = Arpie::ProxyServer.new(Arpie::MarshalProtocol.new, Arpie::SizedProtocol.new)

e.handle MyHandler.new

e.accept do
  server.accept
end

p = Arpie::ProxyClient.new(Arpie::MarshalProtocol.new, Arpie::SizedProtocol.new)
p.connect do |transport|
  TCPSocket.new("127.0.0.1", 51210)
end

puts p.reverse "hi"
# => "ih"

Replay protection

It can happen that a Client loses connection to a Server. In that case, the Transport tries transparently reconnecting by simply invoking the block again that was given to Client#connect. See the Client accessors for modifying this behaviour.

It is assumed that each call, that is being placed, is atomic - eg, no connection losses in between message send and receive; lost messages will be retransmitted. Some Protocol classes provide support for replay protection through in-band UUIDs; though it is not a requirement to implement it. If a UUID is provided in the data stream, the Protocol will not call the handler again for retransmissions, but instead reply with the old, already evaluated value.

Not all protocols support UUIDs; those who do not offer no replay protection, and special care has to be taken elsewhere.

All object-encoding protocols support UUIDs, including YAML and Marshal. XMLRPC does not.

Benchmarks

There is a benchmark script included in the git repository (and in the gem under tools/). A sample output follows; your milage may vary.

      user     system      total        real

native DRb
   1  0.000000   0.000000   0.000000 (  0.000172)
1000  0.110000   0.010000   0.120000 (  0.119767)

Arpie: proxied MarshalProtocol with replay protection through uuidtools
   1  0.000000   0.000000   0.010000 (  0.075373)
1000  0.530000   0.090000   0.600000 (  0.608665)

Arpie: proxied MarshalProtocol without replay protection
   1  0.000000   0.000000   0.000000 (  0.000173)
1000  0.170000   0.020000   0.190000 (  0.194649)