On Sat, Sep 25, 2010 at 07:28:37PM +0900, John Mettraux wrote: > > On Sat, Sep 25, 2010 at 10:22:59AM +0000, Hartog C. de Mik wrote: > > On Sat, Sep 25, 2010 at 07:14:42PM +0900, John Mettraux wrote: > > > > > > On Sat, Sep 25, 2010 at 03:03:40AM -0700, coffeeaddict wrote: > > > > > > > > First off; since this is my first post, let me introduce: > > > > > > > > <snip; introduction> > > > > > > > > Recently I stumbled across ruote as I tried to find a solution for > > > > fortifying an order flow system done in Rails. I steered away from > > > > ruote as there where too many uncertainties. > > > > > > welcome here. I'm curious, what kind of uncertainties are you faced > > > with (it's very useful info for us). > > Many thanks ! > > > Stability: > > - of the available MQ's > > - and the ruby components required > > > > Maturity: > > - of amqp, ruote, ruote-amqp and all components related > > > > Solvability: > > - of problems due to lack of documentation > > I have to protest here, ruote is not lacking documentation. I'm > always struggling to bring more documentation on the table and > always saying "if a point in the documentation is not clear, please > say so".
Nothing personal! ;-) Ruote is the best documented of the components used, my main concern where the amqp related components. Yes; the have rdoc for (almost) every function used, and if you read all of them you can build a notion of how the objects and components are to interface and depend on one and other. It is however very scattered, and requires a lot of creativity of the person with the problem to find the right piece of information. As an example; it took a lot of inspecting AMQP.logging to figure out that the daemon-kit generated classes responded to no queue at all. Finding out where and how to set the reply queue was a matter of using the right search terms in google, which in term require knowledge of how message queues work. If you are new to this domain, it is very hard to get answers from just the documentation. Imho the documentation is then failing to be informative enough. And I agree - no matter how much documentation you write, there will always be complaints. Grtz, Hartog. -- you received this message because you are subscribed to the "ruote users" group. to post : send email to [email protected] to unsubscribe : send email to [email protected] more options : http://groups.google.com/group/openwferu-users?hl=en
