Preserving Business Data and Logic

Result Queue provides abstraction for managing groups of events asynchronously, and zNet further expands API to reuse application's Data and Business Logic.

Any data type, user defined or system, could be wrapped into an Event and submitted to an Active Queue. Conversely, existing business logic expressed via functions or methods, could be registered on the Active Queue to receive an event of specific type.

Typical zNet Event processing and Function registration steps shown in the figure:

Note:

Only first 3 steps in the sequence below executed by the programmer, the rest is managed by zNet.

1. Register MyFunction
2. Register MyReplyHandler
3. Generate and Submit MyData Events to the Result Queue
4. MyData Events Submitted to Worker Queue for Processing
5. Worker Threads pick up MyData Events from the Worker Queue
6. Worker Threads invoke Dispatcher to map MyData Events to MyFunction
7. Worker Threads invoke MyFunction to process MyData Events
8. Update Results to the Result Queue
9. Reply Processing Threads pick up Replies from the Result Queue
10. Reply Processing Threads invoke Dispatcher to match Replies to MyReplyHandler
11. Reply Processing Threads invoke MyReplyHandler to Process MyData Replies