On 8/11/07, cappelaere <[EMAIL PROTECTED]> wrote: > > A simpler approach that may already be there... > > Participant executes activity, sends the request, serializes its > workitem to disk. > If this participant has a unique ID that identify itself by name and > by instance, a URI can be generated to eventually retrieve that > participant instance. > Participant goes away after saving workitem > Response comes back eventually > WfCS reinstantiates participant with received response. Participant > retrieves workitem and processes the response. It eventually releases > workitem to engine. > > This would be easy to do,
Well, OpenWFEru already does it that way. All the expressions have always been asynchronous, else it's not possible to support long running [business] processes. I'm quite busy right now (friend visiting), I will reply with a long mail later, but in short, all you mentioned is already implemented by OpenWFEru else I would never have dared calling it a workflow / BPM engine. I'm quite surprised you didn't already know. TTYL, best regards, -- John Mettraux -///- http://jmettraux.openwfe.org --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "OpenWFEru users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/openwferu-users?hl=en -~----------~----~----~----~------~----~------~--~---
