Non-durable Message Posting

Registered by Kurt Griffiths on 2013-08-13

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

Related branches

Sprints

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.