Skip to content

(connection): handling change in sessionId #7

@rt2zz

Description

@rt2zz

right now there is a bug in the connection registry that if sessionId changes the registry is never updated, since it is only set upon initial connection: https://github.com/rt2zz/edonode/blob/master/index.js#L211

We have two options to solve

  1. require a new connection anytime sessionId changes
  2. listen for sessionId change upon every invocation, and update registry upon change

I am leaning towards option 2 but would like to discuss the pros/cons first.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions