Hi all, I have a situation where I need to submit long-running tasks via a Webware application. These tasks are CPU intensive and can take up to a few minutes to complete.
What I do at the moment is spawn a thread from the servlet to do the processing and let the servlet return to do more work. This works OK but I'd like to find out the status of those jobs and I'd also like to make sure that I'm not trying to do several of these tasks at once because they will bring the sever to a crawl.. So I was thinking of creating a queue and having a worker thread busy away on it, reporting its progress back to the application in some way. Has anyone done this with webware? Advice? Pitfalls to avoid? Thanks. ------------------------------------------------------- This SF.Net email is sponsored by: Oracle 10g Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE. http://ads.osdn.com/?ad_id149&alloc_id66&op=click _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
