commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jon Stevens <...@latchkey.com>
Subject Re: Workflow & Turbine design questions
Date Thu, 29 Nov 2001 01:06:13 GMT
on 11/28/01 4:57 PM, "Brett Gullan" <brettgullan@mac.com> wrote:

> Thanks Jon,
> 
> Would you have any ideas as to how the processing thread might be
> integrated with the Workflow Context and Scope interfaces?
> I need to allow for the fact that in most cases, the web UI would be
> reporting on the activity of the server-based processing. This
> processing would not typically be invoked from the web session; rather
> it is the result of another user or process moving a file into a 'hot'
> directory.

Let me see if I hear you correctly:

#1. User starts workflow process by performing action.
#2. Workflow performs tasks that may take time.
#3. User should not be held up waiting for a response from the server by
background workflow tasks.

So, what the user does is spawn a background thread that executes the
workflow. 

The workflow then updates a database table with regards to its status as
things process through the workflow.

User can then query the database table to find out how far along the
workflow process is.

> P.S: If I get this working, I'd be happy to contribute it!

Great!

-jon


--
To unsubscribe, e-mail:   <mailto:commons-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:commons-dev-help@jakarta.apache.org>


Mime
View raw message