You can schedule tasks to execute in the future. It doesn't guarantee that the task will be executed then, however. You might find the queue backed up, in which case you'll get a long delay then all the tasks executing rapidly.
Alternatively, you can throttle the task queue to execute once per second. But that will affect the whole queue. Jeff On Mon, Feb 20, 2012 at 5:39 PM, marco <marco.m.al...@gmail.com> wrote: > Goal: > > - Transform a request to send ~1000 emails by sending one each X > seconds. > > > Problems found: > > - Cron doesn't allow scheduling for every second (and has to be one > all the time; not just when requested;) > - Using recursive deferred tasks (the first launching the second after > a Thread.sleep(X * 1000) ) seem to break the 30 seconds rule (1000 * X > seconds > 30 seconds) > > Did I miss something? Do you recommend any alternative? > > Thank you. > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine for Java" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-appengine-java/-/nAEat-B1qZQJ. > To post to this group, send email to > google-appengine-java@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine-java+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-appengine-java?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
