We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
(also posted to http-kit as I'm not sure what is the right "layer" to solve this problem)
This isn't so much a "here's a bug in the code" but more of a "is it possible to do X with ring."
I'm using {:client-side [clojurescript] :server-side [clojure, ring, http-kit]}
Now, I want my code to be "robust" vs dropped connections (phone / wifi that often times out.)
Is there a way to simulate this with ring middleware?
Basically, I need it to do things like:
(1) arbitrarily ignore requests (2) arbitrarily delay requests (3) arbitrarily kill web-sockets / comet / long-polling connections
I'd like this to be done in an as "unclean" way as possible -- i.e. instead of calling close on a websocket, have it abruptly killed / time out.
Thanks!
(PS, if this question doesn't belong here / should be posted in a forum somewhere, please let me know.)
The text was updated successfully, but these errors were encountered:
Questions like this should be posted in the Google Group. The issue tracker is just for issues with Ring.
Sorry, something went wrong.
No branches or pull requests
(also posted to http-kit as I'm not sure what is the right "layer" to solve this problem)
This isn't so much a "here's a bug in the code" but more of a "is it possible to do X with ring."
I'm using
{:client-side [clojurescript]
:server-side [clojure, ring, http-kit]}
Now, I want my code to be "robust" vs dropped connections (phone / wifi that often times out.)
Is there a way to simulate this with ring middleware?
Basically, I need it to do things like:
(1) arbitrarily ignore requests
(2) arbitrarily delay requests
(3) arbitrarily kill web-sockets / comet / long-polling connections
I'd like this to be done in an as "unclean" way as possible -- i.e. instead of calling close on a websocket, have it abruptly killed / time out.
Thanks!
(PS, if this question doesn't belong here / should be posted in a forum somewhere, please let me know.)
The text was updated successfully, but these errors were encountered: