QM wrote:
On Thu, Jul 15, 2004 at 11:08:18AM -0400, Jim Van Fleet wrote:
Don't you just love scope creep? ;)
If you only knew. I've definitely earned my wings, but feeling good about myself might not last long in the face of an angry boss. ;-)
In addition to help suggestions from other people, consider this:
1/ if you're sending out the same e-mail to everyone else, what about using a dedicated mailing list tool (such as mailman, listserv, etc)? That way your program sends one e-mail to the mailing list server and it handles distribution.
They each receive different e-mails. It contains a link that they can click on to login to the system without having to identify a username and password.
2/ Do you have to start 1 thread for each e-mail? What about a work queue or leaders/followers setup? (See any book on threading for examples.)
Long story short: these and other thread patterns funnel X number of jobs -- in your case, sending e-mail -- through Y number of threads. X > Y. Say you have 400 addys and 5 threads: each thread should take 80 addresses in sequence.
They definitely don't each need their own thread, that was just the most convenient way to write it at the time. I didn't exactly foresee this problem.
This solution sounds like it could be a winner. I'm certainly more comfortable in code world than configuration world. I'll let you know how it turns out!
Thanks,
Jim
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
