]]>By: rajivseelamhttp://www.sitepoint.com/ironmq-laravel-setup/#comment-113318
Fri, 23 May 2014 03:11:00 +0000http://www.sitepoint.com/?p=81204#comment-113318Bruno suggested that i write a tutorial on handling long running jobs. We can use IronMq class from iron-mq composer package directly and achieve it.
]]>By: rajivseelamhttp://www.sitepoint.com/ironmq-laravel-setup/#comment-113317
Fri, 23 May 2014 03:08:00 +0000http://www.sitepoint.com/?p=81204#comment-113317There is a pull request which makes passing options possible. But it’s not merged for sometime now.
]]>By: MarkLhttp://www.sitepoint.com/ironmq-laravel-setup/#comment-113307
Thu, 22 May 2014 14:18:00 +0000http://www.sitepoint.com/?p=81204#comment-113307Looking forward to the second part. There’s nothing in 4.2 to pass options, unless Taylor will make a last minute change.
]]>By: MarkLhttp://www.sitepoint.com/ironmq-laravel-setup/#comment-113306
Thu, 22 May 2014 14:15:00 +0000http://www.sitepoint.com/?p=81204#comment-113306Chad, thanks. There is nothing in 4.2 that would address this. Someone made a pull request though that hasn’t been accepted in months: https://github.com/laravel/framework/pull/3555
]]>By: rajivseelamhttp://www.sitepoint.com/ironmq-laravel-setup/#comment-113295
Thu, 22 May 2014 04:31:00 +0000http://www.sitepoint.com/?p=81204#comment-113295I think in Laravel 4.2 we will have option to pass timeout (and more options) when pushing to a Queue. I actually didn’t go much deeper as my intention was to help developers who are not using queues yet. Stay tunes for Part 2.
]]>By: rajivseelamhttp://www.sitepoint.com/ironmq-laravel-setup/#comment-113293
Thu, 22 May 2014 04:11:00 +0000http://www.sitepoint.com/?p=81204#comment-113293You are right. But my focus was for beginners who are not making use of queues, and to help them start off immediately. Thanks for input.
]]>By: Chad Arimurahttp://www.sitepoint.com/ironmq-laravel-setup/#comment-113277
Wed, 21 May 2014 17:10:00 +0000http://www.sitepoint.com/?p=81204#comment-113277Hi MarkL,

We (Iron.io) are working on a few solutions around this. If the app knows it’ll take longer than 60s, you can do one of two things: