Skip to content

Seperate open/close port from subscription? #3

@DanielJoyce

Description

@DanielJoyce

Currently when you open a port opened by someone else, you are really subscribing to said port

When you close a port, the underlying serial port is not closed till all other clients close that port as well. Its more like unsubscription.

Should we seperate the two?

  1. Client who opens port gets write-lock to port
  2. Client which subscribes to port gets all read events
  3. Client with writelock can close port
    1. All other clients would be notified of closure
  4. unsubscribe does not close port, leaves port open but releases write locks
  5. other clients can then write lock port to get read/close control of it
  6. client dropping off does not close port either

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