From kato.kiwamu at future.co.jp  Sun Oct  5 11:32:32 2008
From: kato.kiwamu at future.co.jp (kato.kiwamu at future.co.jp)
Date: Mon, 6 Oct 2008 00:32:32 +0900
Subject: [ap4r-user] Thinking of using AP4R
References: <20080922025453.GA12953@apcc21.net>
Message-ID: <14CE73B79D552644B7CBEF0428763DF6015E3F4B@045MAIL.future.co.jp>

Hi Saji,

Thank you for your interested in AP4R and I'm really sorry for this late reply.

> "Background Job", "rudeQ", "Workling" etc, which provide queing and
> background processing. My question is how "AP4R" compares to or is
> different from these others?

One big difference is robustness.
AP4R has 'SAF' function which guarantees a message delivery between your CLIK and AP4R server.
As a result, no matter what happens, for example database and N/W trouble, server down and so on, you don't lose your crunched data. A message is stored in a database before sending AP4R, you can resend the message after recovery from system failure.

The details are as follows.
# you can see a message sequence dialog among rails, ap4r and database.
http://www.slideshare.net/kiwamu/ap4r-on-rubyconf2007/126


Other difference is flexibility for system design.
It's relatively easy to distribute load and control a message flow.
Some patterns are shown below.
http://www.slideshare.net/kiwamu/ap4r-on-rubyconf2007/95


Glad I could be of some help.


Best regards

kiwamu


-----Original Message-----
From: ap4r-user-bounces at rubyforge.org ?? Saji N. Hameed
Sent: 2008/09/22 (?) 11:54
To: ap4r-user at rubyforge.org
Subject: [ap4r-user] Thinking of using AP4R
 
Dear Shino and all,

I am considering on the use of AP4R for our project named "CLIK" for the
time being. CLIK is essentially a Rails front-end to a data crunching
job that ultimately creates a climate prediction. Some of these jobs
only takes a few seconds to finish, some a few minutes, and intensive
calculations 30 minutes or more. Obviously we need to put many of these
jobs in the background and get the output after the job is done.
Actually we use a separate data processing server on a remote machine
using DRb.

I explored a few solutions by googling and found projects like
"Background Job", "rudeQ", "Workling" etc, which provide queing and
background processing. My question is how "AP4R" compares to or is 
different from these others? 

Anyway I am going to explore how to use AP4R in this project by looking
at the HelloWorld example as a guide. FYI, I am only a climatologist and do
not know much about queues, Ruby or Rails and I hoping for good advice
from this list if anything goes wrong.

Yoroshiku,

saji
--


-- 
Saji N. Hameed

APEC Climate Center          				+82 51 668 7470
National Pension Corporation Busan Building 12F         
Yeonsan 2-dong, Yeonje-gu, BUSAN 611705			saji at apcc21.net
KOREA
_______________________________________________
ap4r-user mailing list
ap4r-user at rubyforge.org
http://rubyforge.org/mailman/listinfo/ap4r-user