This has been discussed on tmda-users in the past, however, the outcome of
those past discussions was the reminder that for an individual user those
file may be getting accessed simultaneously anyway due to multiple emails
arriving and being processed in parallel, so weather it's one person getting
hit with a load of new mail (including confirmations) or several users
sharing the same list file it should work fine.

The only caveat is with manually editing a list file which can potentially
cause problems, though I believe those problems are limited to the loss of
any confirmed addresses that were appended to the file after you opened it
for editing but before you saved your changes.

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of David Hoffman
Sent: Wednesday, March 16, 2005 7:20 AM
To: Michael; [email protected]
Subject: Re: Shared confirmed file?

--- Michael <[EMAIL PROTECTED]> wrote:
> But the problem is that I am concerned about multiple processes
> writing to
> the shared 'confirmed' file ....

I'm not sure that is a problem. For one thing the only thing that is
taking place when the file is written is a new address is appended to
the end of the file. That can't take more than a few CPU cycles. The
chances of two processes hitting it at the exact same time is going to
be rare. Not to mention that if the entire file is not being
re-written, then it's simply the same thing as doing:

echo "[EMAIL PROTECTED]" >> confirmed.list

And that again only takes milliseconds to complete.

I don't think that is something that would present a problem.




                
__________________________________ 
Do you Yahoo!? 
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/ 
_____________________________________________
tmda-users mailing list ([email protected])
http://tmda.net/lists/listinfo/tmda-users
_____________________________________________
tmda-users mailing list ([email protected])
http://tmda.net/lists/listinfo/tmda-users

Reply via email to