Issue 10: evaluate django-cron or other in-process solutions for sending
mail
http://code.google.com/p/django-mailer/issues/detail?id=10
Comment #1 by brosner:
Oh goodness. django-cron would be the worst thing for django-mailer.
django-cron is not very reliable. It is
triggered based on the request. When a request comes in it checks if
something needs to run. Which makes it
horribly unreliable. On top of that it does it processing in the webserver.
This makes it horrible bound to the
webserver and will hurt performance of your web application. I would only
see django-cron beneifical in very
strictly hosted platforms.
django-mailer has been written in such way that uses a little system
resources in a true cron situation. When
cron fires off a process a file lock is made to prevent other processes
from hogging resources. You will only
ever have to worry about two processes running at a single moment in time.
One doing something another
check to see if it can do something and then dies off. While this isn't
necessary the best way in situation with
*tons* of e-mails it certainly allows for a distributed system. We are
working on django-engine which will
make django-mailer engine bits much more flexible allowing for persistent
processes and queues for more
performant processing.
Issue attribute updates:
Status: Invalid
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"pinax-updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/pinax-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
