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
in here bufferevent_ssl is doing a evbuffer_drain without unfreezing and freezing the output . And further more, the consider_writing() return code isn't actually checked, which means if the buffer is freezed from outside , the bufferevent_ssl will repeatedly send same content over and over without draining it from the buffeer.
The text was updated successfully, but these errors were encountered:
actually what is the protocol for freeze and unfreeze? should evbuffer be kept frozen most of the time or should it not ? It's unclear from the doc. evbuffer_sock , evbuffer_sockpari, and evbuffer_ssl does different things. evhttp also kept the buffer freezed
@azat : is there documentation around what freezing is intended for and the what is the right protocol here? (For example: should various layer keep buffer freezed in front at all time, and unfreezed in the tail or something else? )
is there documentation around what freezing is intended for and the what is the right protocol here? (For example: should various layer keep buffer freezed in front at all time, and unfreezed in the tail or something else? )
There is not a lot of developers-related documentation (sadly), but all bufferevents implementations should follow the same patterns or describe why it is not possible. I don't see any reasons for not freeze the buffer for SSL.
libevent/bufferevent_ssl.c
Line 417 in bca2652
in here bufferevent_ssl is doing a evbuffer_drain without unfreezing and freezing the output . And further more, the consider_writing() return code isn't actually checked, which means if the buffer is freezed from outside , the bufferevent_ssl will repeatedly send same content over and over without draining it from the buffeer.
The text was updated successfully, but these errors were encountered: