[ap4r-devel] [ ap4r-Patches-14722 ] valid_at parameter which allows to schedue message handling
noreply at rubyforge.org
noreply at rubyforge.org
Wed Jan 9 08:58:20 EST 2008
Patches item #14722, was opened at 2007-10-15 17:03
You can respond by visiting:
http://rubyforge.org/tracker/?func=detail&atid=6912&aid=14722&group_id=1765
Category: None
Group: None
Status: Open
>Resolution: Postponed
>Priority: 4
Submitted By: Pawel Krzesniak (imo)
Assigned to: Nobody (None)
Summary: valid_at parameter which allows to schedue message handling
Initial Comment:
I added optional field messages which allows to handle specific action not before given timestamp. Such functionality allows to schedule some actions in the future, which could be nice feature.
If valid_at parameter is not given ap4r process message immediately, which is old behaviour.
example usage:
ap4r.async_to({:action => :test}, {:id => 123}, {:valid_at => Time.now.to_i + 3, :priority => 1})
----------------------------------------------------------------------
>Comment By: shunichi shinohara (shino)
Date: 2008-01-09 22:58
Message:
Nice extention!
The Selector is one of useful features of reliable-msg, so I want to take advantage of that.
I am anxious about the case that:
large number of messages in a queue, and
those are "not-valid-yet".
For example, messages those should be processed at midnight.
I parhaps should consider some kind of scheduling.
----------------------------------------------------------------------
You can respond by visiting:
http://rubyforge.org/tracker/?func=detail&atid=6912&aid=14722&group_id=1765
More information about the ap4r-devel
mailing list