long running mailets

[Bosco So]

What are some strategies for dealing with long running mailets? If I'm 
personalizing messages for a list of 65,000 people, that thread is bound 
to take some time. Should I break the list into chunks and spawn 
separate threads to handle the chunks? Or stay in one thread and assume 
the spooler will spawn off multiple threads for actual delivery?

How do I deal with external events like James shutdown? Should I set a 
flag in the destroy() method and check it when I'm looping through my 
members in service()?

What are some general best practices?

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BOSCO SO                                   www.groundspring.org
Senior Software Engineer, Groundspring.org.  Growing nonprofits
with Internet tools and training.
DonateNow:  Accept credit card donations through your website
EmailNow:  Send eNewsletters and communicate with supporters
   ebase:  Manage your stakeholder relationships
Groundspring.org, P.O. Box 29256, San Francisco, CA 94129-0256
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]