Michael Check wrote: > Well, in our current setup, it's not possible cause we're running the > web server on the same machine as the 4D server (tsk, tsk, I know). > > But can you elaborate on 4DIC blocking the server? The mails we send > are only "forgotten password" mails and some "registration > confirmations". I would guess that we send around 50-100 per day at > most at this time. > > In what ways might this scenario be susceptible to being blocked by 4DIC? > The problem is that the 4DIC commands have historically run synchronously. Sometimes the plugin call to send a mail message will have to wait for the server to respond. When this happens other 4D processes (like your web server) have to wait.
However, I've been told that there have been some improvements in 4DIC with versions 2003 and later. I haven't thoroughly tested this, but think that the situation appears to have improved. -- Brad > Thanks > > Michael Check > > On Tue, Jan 13, 2009 at 3:06 PM, Aparajita Fishman > <[email protected]> wrote: > >>> If you will possibly have this code running on more than one machine, >>> then use a semaphore to ensure that two processes don't process the >>> queue at the same time. >>> >> If possible, run the email sending on a machine other than the web server so >> you don't have problems with 4DIC blocking the server. >> >> Regards, >> >> Aparajita >> www.aparajitaworld.com >> >> "If you dare to fail, you are bound to succeed." >> - Sri Chinmoy | www.srichinmoy.org >> >> >> _______________________________________________ >> Active4D-dev mailing list >> [email protected] >> http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev >> Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/ >> >> > > > > _______________________________________________ Active4D-dev mailing list [email protected] http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
