Skip to content
This repository has been archived by the owner on Mar 11, 2022. It is now read-only.

Implement EntityDiscoveryServer.ReportError according to new spec recommendations #9

Open
marcellanz opened this issue Oct 22, 2019 · 0 comments
Labels
good first issue Good for newcomers

Comments

@marcellanz
Copy link
Contributor

As discussed on todays constributors call, ReportError should:

  • Should be used for informational purposes only—the message MUST be reported to the developer. Not logged as DEBUG. Typically that would mean writing it to STDOUT but it may go somewhere else depending on the language used.
  • If stream is closed afterwards, then it should passivate the entity (just as normal)

therefore, if the proxy does not close the stream, the entity will receive further commands/events for the entity. The user (developer) should receive the error and then decides what to do. It is advised to make the error discoverable, most probably through writing it to stderr/stdout.

@marcellanz marcellanz added the good first issue Good for newcomers label May 6, 2020
@marcellanz marcellanz changed the title implement EntityDiscoveryServer.ReportError according to new spec recommendations Implement EntityDiscoveryServer.ReportError according to new spec recommendations Oct 9, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

1 participant