Hi Alex,
2007/10/1, Alex Graul <[EMAIL PROTECTED]>:
> We've chosen AP4R for our project which involves a lot of very db
> heavy/high load processes that need to be
Thank you very much for your interests in AP4R.
I answer and comment (and ask you back :-) ) on some of your questions
and will answer in another mail on the others.
> Does AP4R support priorities from reliable-messenging? I assume 0 is
> the lowest, is there a highest?
Now priorities are ignored in AP4R('s dispatchers). I want to know how
you intend
to use priorities or how differently treat them.
> Does AP4r support repeat messages (reliable messaging apparently
> does, though I can find zero documentation)?
AP4R doesn't support it now. Which side, client(async_to) side or server
(dispatchers) side, do you need repeating?
> Any ballpark timeframe on stable carriers?
It's very difficult :-< . With carriers, there may happen
pitch-and-catch of messages
between AP4R servers. The present implementation is rather naive, I think.
> Is postgres support stable?
YES.
> 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?
I will write a mail about those later.
Thanks,
shino (Shunichi Shinohara)
_______________________________________________
ap4r-user mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/ap4r-user
