Hi Glen and Sebastian. Thanks for clarifying this in text and POD.
I'm more or less exploring the possibilities of Minion. If it were possible to get async notifications back, this would be a magnificent way to bridge the sync and async worlds! For most of my intended uses of Minion, it's perfectly fine to enqueue a job, keep track of the jobid and return from the route. But there are also some shorter blocking operations that I was curious if it could handle. On 27 January 2015 at 00:14, sri <[email protected]> wrote: > The main intent of minion is to execute long running, blocking tasks that >> would take longer than the life cycle of a request, so return values >> aren't a feature. > > > They actually have become a (minor) feature recently, since it was > convenient to turn the old error field into a generic result field. But we > do indeed not support async notifications for job state transitions, for > the reason you mentioned. > > -- > sebastian > > -- > You received this message because you are subscribed to the Google Groups > "Mojolicious" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/mojolicious. > For more options, visit https://groups.google.com/d/optout. > -- Pelle Research is what I'm doing when I don't know what I'm doing. - Wernher von Braun -- You received this message because you are subscribed to the Google Groups "Mojolicious" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/mojolicious. For more options, visit https://groups.google.com/d/optout.
