Skip to content

Inconsistent semantics for channel related events #20

Closed
@anderspkd

Description

@anderspkd

Currently there are two channel related events: sim::EventType::SEND and sim::EventType::RECV. The former is created when data is sent, while the latter is created when data is read from a channel.

Therefore, sim::EvenType::SEND models the data that goes onto a network, but sim::EventType::RECV only models the data from the network that is useful to a protocol. This creates a skewed interpretation of results, and may make a network seem less saturated than it actually is (e.g., consider a protocol where everyone sends a message to everyone else, but only reads the message sent by e.g., party 0.)

Changes
Rename sim::EventType::RECV to sim::EventType::READ and update documentation to make it clear what it models.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions