You are viewing a plain text version of this content. The canonical link for it is here.
Posted to proton@qpid.apache.org by "Cliff Jansen (JIRA)" <ji...@apache.org> on 2014/05/21 23:36:38 UTC
[jira] [Created] (PROTON-584) Proton-c transport reserves large
buffers for brief use
Cliff Jansen created PROTON-584:
-----------------------------------
Summary: Proton-c transport reserves large buffers for brief use
Key: PROTON-584
URL: https://issues.apache.org/jira/browse/PROTON-584
Project: Qpid Proton
Issue Type: Improvement
Components: proton-c
Affects Versions: 0.8
Reporter: Cliff Jansen
When processing transfer frames for incoming messages, Proton requires a temporary buffer holding the whole transfer frame briefly in contiguous space in the transport before moving it to the engine proper which holds the content in a separate memory area.
pn_transport_capacity grows the buffer in the non-ssl case (transport->input_buf), and openssl.c largely duplicates the code (including the comment about "no limit") for ssl->inbuf for ssl connections.
Either way, a large message will trigger reserving a similarly large buffer for the rest of the life of the connection.
Is it necessary for the transport to buffer the whole message body and hang on to that memory?
--
This message was sent by Atlassian JIRA
(v6.2#6252)