on 11/28/01 4:57 PM, "Brett Gullan" <[EMAIL PROTECTED]> 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:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
