Hi There, First off a big thanks for this great engine. I've read a lot of postings talking about the goal of being able to rapidly prototype and prove concepts with Openwferu - rather than having everything out of the box - that approach really seems to work wonders!
Having said that, I do have a question about the best way to approach a modification to ruote_rest - that is, enabling the use of wait_for. I realise that wait_for is designed more for unit tests, and isn't part of a pure BP approach, however I have this edge case: 1. User provides input parameters to a LaunchItem 2. User triggers the process 3. Engine processes the flow, returns the results to the waiting user. This could be achieved with callbacks etc, but in my mind the cleanest way is a simple wait_for. Is there any major side-effect to having a configurable wait for in the post "/processes" block? Or should there perhaps be a blocking engine implementation? Many thanks, Corin --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
