AP4R First release! (version 0.1.0)

We are pleased to announce the FIRST release of AP4R.
http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-talk/211937

[ANN] AP4R, Asynchronous Processing for Ruby, initial release

We are pleased to announce the FIRST release of AP4R. http://rubyforge.org/projects/ap4r/

It completely owes message persistence to reliable-msg.
http://trac.labnotes.org/cgi-bin/trac.cgi/wiki/Ruby/ReliableMessaging

Concepets added to reliable-msg are these two:

  • build-in message dispatcher

We added message "dispatcher"s as threads.
When amessage arrives and queued by a reliable-meg server, a "dispatcher" gets it and invoke some action. Invocation are now implemented as XML-RPC call.
Thanks to dispatchers, application developers can write logic as web applications, e.g. rails actions.

  • load balancing among many reliable-msg servers

We added kind of "routing" logic with "brige"s which get messages from a reliable-msg server and put them to another reliable-msg server (also as threads). We aim load balancing of async pocesses over many machines(boxes). This probably plays an important role in systems with intensive asynchronous works.
Current implementation just adds threads which get messages from other reliable-msg servers and put them into a local reliable-msg server.


These two are just proof-of-concept implementation now. We want to improve quality and add functionalities, please give us advices and comments.

I want to express my thanks to Ruby community, especially ruby itself and reliable-msg.


(note) Entries in this blog are personal opinions of mine (shino),
and are NOT of the company which I belongs to.


日本語エントリはこちら

いたわさににほんしゅ - [Ruby][AP4R] 祝! AP4R 初リリース (version 0.1.0)
http://d.hatena.ne.jp/ita-wasa/20060908/1157693946