http://ap4r.rubyforge.org/wiki/wiki.pl?GettingStarted
[list=1]
[*]1. Business logics can be implemented as simple Web applications, or ruby code, whether it's called asynchronously or synchronously.
[*] 2. Asynchronous messaging is reliable by RDBMS persistence (now MySQL only) or file persistence, under the favor of reliable-msg.
[*] 3. Load balancing over multiple AP4R processes on single/multiple server(s) is supported.
[*] 4. Asynchronous logics are called via various protocols, such as XML-RPC, SOAP, HTTP POST, and more.
[/list]
未完待续`````````````````````
http://www.infoq.com/cn/news/2007/06/messaging-with-ap4r
[list=1]
[*]1. Business logics can be implemented as simple Web applications, or ruby code, whether it's called asynchronously or synchronously.
[*] 2. Asynchronous messaging is reliable by RDBMS persistence (now MySQL only) or file persistence, under the favor of reliable-msg.
[*] 3. Load balancing over multiple AP4R processes on single/multiple server(s) is supported.
[*] 4. Asynchronous logics are called via various protocols, such as XML-RPC, SOAP, HTTP POST, and more.
[/list]
未完待续`````````````````````
http://www.infoq.com/cn/news/2007/06/messaging-with-ap4r