Hello,
First of all, thankyou very much for your incredible work on AP4R,
it's shaping up into one hell of an async architecture.
We've chosen AP4R for our project which involves a lot of very db
heavy/high load processes that need to be
run on a regular basis so it's perfect for us. We've already got it
up and running and are in the process of moving
code around and kicking the wheels, so to speak. We do however have a
few questions:
Does AP4R support priorities from reliable-messenging? I assume 0 is
the lowest, is there a highest?
Does AP4r support repeat messages (reliable messaging apparently
does, though I can find zero documentation)?
If so how does it work and what are the options?
If I'm understanding Carriers correctly we can have say one server
with a queue which is then checked by other AP4R
servers which then execute those messages on local threads. Can those
servers accept messages to a local queue as
well or do they just take messages over carrier?
When we do async_to calls using the controller/action format
(ap4r.async_to( {:controller => ...', :action ="" '....'} ,,,)) the
message seems to keep the port number of the app that called it,
obviously we can specify a full url and get round this
but is there a more elegant solution?
Any ballpark timeframe on stable carriers?
Is postgres support stable?
Cheers,
Alex Graul
_______________________________________________ ap4r-user mailing list [email protected] http://rubyforge.org/mailman/listinfo/ap4r-user
