Well another point is that if I want to send time-sensitive info, it would be impossible (i.e. with your method, you are running the sending throughout the entire day, but in some cases almost-instant sending is required).
Another problem worth mentioning is that mass-fetching from the datastore (all the emails) would not work in the current appengine... On Dec 18, 9:50 pm, Alexander Kojevnikov <alexan...@kojevnikov.com> wrote: > > That would work well for a small amount of users. But what if my app > > grows to like 5,000 emails? Your solution would definitely not work > > well at that point! > > I agree that it's far from being perfect, but I don't see why it > wouldn't scale. I currently send about 100 emails a day, if this > number grows, I would just need to buy more quota and ping the mail > sender URL more frequently (every 17 seconds for 5,000 emails a day). > > > Do you maybe know of an external service that would allow me to set up > > s/t to "broadcast" to many url's or is there another way that i'm > > "missing"? > > Google will eventually roll out a solution for background processing, > you can switch to it when it's available. > > Also, a few workarounds have been discussed in this group, just search > it for "background". > > --www.muspy.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
