What do background and asynchronous really mean? about rails_workflow HOT 2 OPEN

@joshco according to your questions:

1. A process gets completed when all operations are completed. The engine is ready for using async - I just need to update runners (I don't have it in an open source gem but it was implemented in non-open source versions). Let's say you have order processing workflow. It processes orders and one operation starts subprocess which covers storage provisioning. Order process (parent process) doesn't care for it - it just starts it as a child process but doesn't need to wait for this child process to complete. If you mark the operation as an async - process will be able to complete having this operation still in progress. Most common usage is for subprocess operations - they start subprocesses and parent process doesn't need to wait for child process to complete of async subprocesses.

2. If you want to have some validations before completing operation - there are at least three ways to implement it. You can contact me in skype (maxim.madzhuga) - and I will be able to describe them and answer your questions.

3. I tried to implement pretty simple dependency resolution here in rails_workflow engine - let me know if something looks complex to you :)

Do you have any other questions? Some of non-opensorce realizations of an engine were modified to cover complex errors management, configuration caching, user groups/roles permission etc.

from rails_workflow.

@joshco I am trying to get some feedback from people using rails_workflow - can you contact me ([email protected])?

from rails_workflow.