>>Could you break your task into little chunks and run it as a state machine
>>with a permanant process that runs state 'chunks' and records progress?

Interesting idea but the tasks that I want to run have already been developed in a 
stand-alone way. Wrapping them into a thread or keeping them standalone and making 
them coordinate via some shared-state server wouldn't be too hard but organizing them 
as you suggest sounds like it could be some work. 

        -----Original Message----- 
        From: Shayne ONeill [mailto:[EMAIL PROTECTED] 
        Sent: Sat 22/05/2004 03:12 
        To: Ian Sparks 
        Cc: Webware-Discuss (E-mail) 
        Subject: RE: [Webware-discuss] Task-Queue using Webware...
        
        


        Could you break your task into little chunks and run it as a state machine
        with a permanant process that runs state 'chunks' and records progress?
        Its an odd way to do it, but it lets you run it all in a single thread.
        
        --
        Shayne O'Neill
        http://perth.indymedia.org
        I know how hard it is for you to put food on your family."
         ----George W. Bush
        
        On Fri, 21 May 2004, Ian Sparks wrote:
        
        > Sorry...didn't CC the list.
        >
        > Nick Murtagh wrote:
        > >>
        > I do this using a database table that records the name, status (running,
        > not running, error) and progress (1 - 100%) of each thread.
        > <<
        >
        > So you use a number of worker threads? Since I'm concerned about swamping my 
server I think I'll stick to one.
        >
        > Where do you initialize your worker threads? From a servlet or from some 
startup hook in WebWare (if so, where is the best place to put this) ?
        >
        > Thanks!
        >
        > -----Original Message-----
        > From: Nick Murtagh [mailto:[EMAIL PROTECTED]
        > Sent: Friday, May 21, 2004 11:45 AM
        > To: Webware-Discuss (E-mail)
        > Subject: Re: [Webware-discuss] Task-Queue using Webware...
        >
        >
        > Ian Sparks wrote:
        > > Has anyone done this with webware? Advice? Pitfalls to avoid?
        >
        > I do this using a database table that records the name, status (running,
        > not running, error) and progress (1 - 100%) of each thread. The threads
        > themselves are responsible for keeping this updated. You could also use
        > this table as a sort of mutex / semaphore, assuming your database can
        > give you the required transaction isolation...
        >
        >
        > -------------------------------------------------------
        > 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_id=3149&alloc_id=8166&op=click
        > _______________________________________________
        > Webware-discuss mailing list
        > [EMAIL PROTECTED]
        > https://lists.sourceforge.net/lists/listinfo/webware-discuss
        >
        >
        > -------------------------------------------------------
        > 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_idÂ66&op=click
        > _______________________________________________
        > Webware-discuss mailing list
        > [EMAIL PROTECTED]
        > https://lists.sourceforge.net/lists/listinfo/webware-discuss
        >
        

Reply via email to