I've been looking over your RIFE/Workflow project and i'm intrigued by it's possible application. I have the need to write a workflow engine...many of the "job steps" that need to be performed by this action are long latency operations ...i.e. calls to external web services which may take many seconds before I can continue doing work myself. It seems like this might be a natural fit for utilizing continuations in some fashion.
The primary question I have though is looking at your implementation of com.uwyn.rifewf.Task and com.uwyn.rifewf.run.TaskRunner classes, after calling the waitForEvent method, all continuations waiting for a given Event class will be resumed. But I'm fearing I need to be more grainular about when i resume a given continuation. For instance I might have 20 continuations waiting on 20 different Web Service calls to the same web service concurrently each continuation can only continue when it's specific request comes back, not when any of the 20 calls recieve their response. The only way I can think to handle it is to have all the contuations wake up and see if this given Event pertains to them...that is that this is the response to the request that they previously issued....and if it's not...then they waitForEvent again. But that seems quite inefficient. So could you tell me if I'm thinking about this correctly and any suggestions to solve this type of problem with continuations. Depending on your response I plan to prototype a solution with RIFE/ workflow ASAP. Thank you for your time, Andrew --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "rife-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/rife-users?hl=en -~----------~----~----~----~------~----~------~--~---
