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

Think of generic ACK protocol #77

Open
soygul opened this issue Jan 3, 2016 · 1 comment
Open

Think of generic ACK protocol #77

soygul opened this issue Jan 3, 2016 · 1 comment

Comments

@soygul
Copy link
Member

soygul commented Jan 3, 2016

msg.recv -> [1,2,3]
[1,2,3] <- msg.ack (ack each accepted message individually in an array batch?)

In the above scenario, client connects and first call is msg.recv which should get all pending messages in a single Msg.Response, which is an array of messages. But how shall we acknowledge them? Shall we ACK the ACK? Same goes for all messages essentially so we might think of a generic ACK system where messages ACKed back-and-forth based on importance. i.e. msg.recv ACK by server & ACK the ACK by client, as this initial call is very important.

@soygul
Copy link
Member Author

soygul commented Feb 9, 2016

Or something like MQTT? or Thrift w/ Go implementation?

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

1 participant