coder / coder/websocket

Improve control on close reason

Aperta
#454 0 commenti 1 reazione 0 assegnatari Vedi su GitHub
Lingua principale
Go
Stelle
5.5k
Fork
372
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Descrizione

What's the intended usage pattern of the Reader and Writer context w.r.t. closing the connection from the server side?

It seems like the connection is closed automatically by the reader / writer when the context is cancelled. However, I don't have any way of impacting the status and reason for that close within the reader / writer.

Is the intention that the user of the reader / writer closes the connection with the status and reason they want and let the writer / reader return?

Another option could be that this package would support influencing the close status and reason via an error provided as context cancellation cause.

WDYT?

Guida per i contributori

Nessuna guida per i contributori indicizzata per questo repository

Valutazione

Questa issue non è ancora stata valutata.

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.