IntraVert 2.0 (async discussion)

Currently in IntraVert 1.0 a Request is a list of Ops executed in series. IntraVert 2.0 could take more advantage of the async nature of VertX and it's module system.

• Can we unity the request/op/response module to use Vertx's JSON object all the way through
• What is the overhead of passing requests between modules?
• Is there anyway to use a module locally without serializing json objects and sending them over the eventbus? @edwardcapriolo yes, latest vert.x threading is in master (marked as 2.0).
• How is the intraState effected are their concurrency issues?
• How can we make operations depended on previous other steps (dependency language) ?
• can we return the results of ops to the client while others are still processing?