21–30 of 71 posts
Since I'm doing something similar in an enterprise environment I suggest you to add , to each cron, a dates black-list. I mean a list of dates in which you do not want the job to be executed ( Christmas , Easter etc). Kudos for the clean documentation
Love it. I'm a big believer in choosing the right vocabulary. Half of the fogginess in communicating ideas comes from bad vocabulary, and matching that vocabulary to your user base. For example, "signal" is a great word that describes the behavior. "Delegate" is also decent. "Dictionary" is not a good word. If you don't know that a dictionary is a key value store, it's not very obvious. Same with "hash"; unless you'v…
Would creating 60 jobs polling the same URL at 1 min intervals translate to the site getting polled every second? Or is there batching/coalescing of the same-URL jobs?
The crons are spaced out over time. This is actually why i took so long to launch the site. I've used the prototype version of this for a long time. The app is written in node so it is incredibly fast, like destroy the internet fast. That is why email confirmations are required and accounts are limited to 5 crons each. I will add a captcha on account confirmation shortly as well.
Google does something like this: http://support.google.com/a/bin/answer.py?hl=en&answer=6... -- their alternatives also include changing DNS to add a dummy TXT record.
Would creating 60 jobs polling the same URL at 1 min intervals translate to the site getting polled every second? Or is there batching/coalescing of the same-URL jobs?
The crons are spaced out over time. This is actually why i took so long to launch the site. I've used the prototype version of this for a long time. The app is written in node so it is incredibly fast, like destroy the internet fast. That is why email confirmations are required and accounts are limited to 5 crons each. I will add a captcha on account confirmation shortly as well.
what
curl -X POST http://127.0.0.1:7931/api/callbacks/ \
-d "url=http://example.com/messages/1/send/" \
-d "eta=2012-03-25T08:00:00Z"
Love it. I'm a big believer in choosing the right vocabulary. Half of the fogginess in communicating ideas comes from bad vocabulary, and matching that vocabulary to your user base. For example, "signal" is a great word that describes the behavior. "Delegate" is also decent. "Dictionary" is not a good word. If you don't know that a dictionary is a key value store, it's not very obvious. Same with "hash"; unless you'v…
Since you're being pedantic, the word you were looking for was "pedantry", not pedanticism :-)
Sorry, I could not resist! ;-)
Very cool. And kudos on the clean documentation.
If I was looking to hire, this entire project would shout HIRE HIM!