Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

error handling strategy #4

Open
djzurawski opened this issue Aug 22, 2017 · 5 comments
Open

error handling strategy #4

djzurawski opened this issue Aug 22, 2017 · 5 comments

Comments

@djzurawski
Copy link
Contributor

It would be neat if when exposing an api with think.peer, the user could provide a function to be called in case of errors (middleware-esque)

@djzurawski
Copy link
Contributor Author

@rosejn
Copy link
Contributor

rosejn commented Aug 22, 2017

Good idea. I'll look into it.

@charlesg3
Copy link
Contributor

Do you mean on the front end or the back? On the front end there is an optional "error-fn" That can be provided to the "websocket-chan" and "request" functions that gets called on error

@harold
Copy link
Contributor

harold commented Aug 23, 2017

Backend.

@charlesg3
Copy link
Contributor

charlesg3 commented Aug 23, 2017

Ah -- it would definitely be nice to have middleware on the backend, for instance having some logging and authentication layers seem like near-term needs. Especially if we can manage a "session" associated with each peer.

@fjsousa fjsousa self-assigned this Apr 15, 2020
@fjsousa fjsousa removed their assignment May 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants