DavidA wrote:
> An alternative that stays inside Django is to setup a trigger in cron
> (or NT's Task Scheduler) that gets a URL every few minutes and the view
> code for that URL does the email processing you mention. You avoid
> creating a true daemon/service just by "waking" up periodically
DavidA wrote:
>
> Russell Blau wrote:
>
>>Ahh, thanks, it always helps to take the blinders off. The only downside is
>>that I have to learn how to use yet another software package. ;-)
>
>
> An alternative that stays inside Django is to setup a trigger in cron
> (or NT's Task Scheduler)
Russell Blau wrote:
> Ahh, thanks, it always helps to take the blinders off. The only downside is
> that I have to learn how to use yet another software package. ;-)
An alternative that stays inside Django is to setup a trigger in cron
(or NT's Task Scheduler) that gets a URL every few
"spacedman" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
>
> Wouldn't it be better to setup 'procmail' to process incoming emails as
> they arrive. Then your procmail script could update the database.
Ahh, thanks, it always helps to take the blinders off. The only downside is
Wouldn't it be better to setup 'procmail' to process incoming emails as
they arrive. Then your procmail script could update the database. As
long as you are using a decent database server (*cough*POSTGRES*cough*)
then concurrency shouldnt be a problem.
I'm kind of a newbie at this (web applications, that is, not Python
programming), so I'd appreciate any advice others can offer.
I'm developing a Django app (post-M-R) that will communicate by email with
some remote hosts (which are running archaic software that can't easily be
updated to use
6 matches
Mail list logo
