> -----Original Message----- > From: news [mailto:[EMAIL PROTECTED] Behalf Of Vic > Sent: Monday, December 06, 2004 1:44 PM > To: [EMAIL PROTECTED] > Subject: Re: [OT]Threads and Servlets Question > > > A common solution I use is to have async processes run by cron or > similar to prepare and massage data. A sperate application that runs > every few minutes and dies. > > A long time ago it was said "Batch is bread and butter of IT. View is > only the icing on the cake." > > .V > > > Jan Fetyko wrote: > > This is interesting, > > > > let me ask another related question : > > > > What about a thread (started from the Action) that just > resizes an image and saves it to a file system ? Would that > be also a bad idea ?
Depends on how important the image is... what happens if the server dies? Your image resize is not done and you may have no idea that that's what happened. Using a mechanism like JMS, or Producer/Consumer allows you to save state and pick up where you left off. As Craig said it's up to you do any error handling inside the thread, which is not as easy as it sounds. > > > > Jano > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
