Skip to content

Think of generic ACK protocol #77

@soygul

Description

@soygul
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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions