Feature #25
MailBox architecture for fully asynchronous operations
| Status: | Rejected | Start date: | 02/17/2016 | |
|---|---|---|---|---|
| Priority: | Normal (Code 4) | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | - | |||
| Target version: | - |
Description
API shall be implemented to support mailbox like operations. When system is accessed by asynchronous channels and operations are forwarded to another system, then we shall support of saving the "request state" in disk (file or DB). Then when response is received, by lookup key context data is restored for specified process. If timeout occurs, then process should receive context data + timeout flag.
History
#1 Updated by Madars over 6 years ago
The fully async operations could be made by processes doing tpcall and setting some new flag, which would dump the current process out to disk while waiting for answer. Main while the image of process which is idling on services (wait for message), should be loaded. Once response is receive, the response shall be queued and response shall be loaded into process from disk/ramdrive.
#2 Updated by Madars over 1 year ago
- Status changed from New to Rejected