You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I find the doc is unclear about whether or not hackney preserves state when reusing a connection e.g. read cookies and send them back on the next request.
I've read the code and i'm truly sure it does, and if it wouldn't the point of reusing a connection would be zero, but i think the readme should be more explicit about that. Because that's what I was looking for when I found hackney, and I bet there are many people looking for this functionality.
I'm sorry not providing a pull request, but I'm not fluent enough in english.
edit: btw, the readme file mentions hackney_http_proxy:connect_proxy/5 which doens't seem to exist anymore.
The text was updated successfully, but these errors were encountered:
Right now, reuse means reuse the socket. No state is kept and you need to store the cookie somewhere in your application if you need it.
The point of reusing connections is to reduce the number of opened connections on your machines. If your server is handling keepalive then you have good chances to reuse the last connection.
Hi,
I find the doc is unclear about whether or not hackney preserves state when reusing a connection e.g. read cookies and send them back on the next request.
I've read the code and i'm truly sure it does, and if it wouldn't the point of reusing a connection would be zero, but i think the readme should be more explicit about that. Because that's what I was looking for when I found hackney, and I bet there are many people looking for this functionality.
I'm sorry not providing a pull request, but I'm not fluent enough in english.
edit: btw, the readme file mentions
hackney_http_proxy:connect_proxy/5
which doens't seem to exist anymore.The text was updated successfully, but these errors were encountered: