Non-durable Message Posting
Registered by
Kurt Griffiths
Clients could implement their own “fire and forget” semantics if they don’t want to wait for our response. We can look into the possibility of (optionally) responding prior to replicating and/or writing to disk for users who are willing to risk it.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- New
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
(?)