7 comments

[ 4.1 ms ] story [ 26.4 ms ] thread
never heard of iron worker...i do a similar thing with delayed_job and https://www.tropo.com/
Now you have! :) IronWorker is like a hosted delayed_job.. meaning you never worry about servers. Another benefit is if you have to scale up your workers, we've got thousands of cores available at any given moment.
If you need schedulability for outgoing calls / SMSes in Twilio send me an email. I have bled all over this topic; you can avoid some of the more painful mistakes by talking to me. Without casting aspersions about people attempting to increase the community's knowledge through blog posts let me say that it goes substantially deeper than an N-line code snippet.
We'd love to hear more... IronWorker acts as "cron in the cloud" so you're right it's not overly complicated.
Can you give a brief summary of the issues here. I'm not planning on implementing this for anything, but I'm curious why it's more complicated than it appears to be.
It's really not that complicated. The example on github works and you can try it out pretty easily to see for yourself. And if you need any help or have any questions, you can get some real-time help in our public chat: http://get.iron.io/chat
Twilio should simply add "send_date_time" or "call_date_time" param. I wonder why they have not?