Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add descriptions to ORMPPort or Msgport? #29

Open
hackfisher opened this issue May 22, 2024 · 0 comments
Open

Add descriptions to ORMPPort or Msgport? #29

hackfisher opened this issue May 22, 2024 · 0 comments
Assignees

Comments

@hackfisher
Copy link
Contributor

The application business layer may consist of one or more messages within the same transaction, and these usually require messages to follow a specific sequence or process. After an ORMPPort message is delivered, it is considered completed regardless of whether the dispatch was successful, and it cannot be retried, which is relatively simple. RetryORMPPort, on the other hand, must finish/close/retry/clear any failed dispatch messages before proceeding with subsequent messages in the transaction. Otherwise, forgetting to close previous messages in the transaction may disrupt the order of messages (or the transaction process).

应用业务层同一个事务可能由一个或多个message组成,他们一般要求messages按序或按流程。ORMPPort消息递送后,无论是否dispatch成功都算做消息完成且无法重试,比较简单。RetryORMPPort必须要finish/close/retry/clear dispatch失败的message之后,再继续完成该事务的后续消息,否则忘记关闭事物中的前序消息有可能破坏该事务中消息的顺序(或事务流程)。

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants