> ok. That sounds good. But, what I'm seeing is that the SSL client
> hangs when the message size is more than 16KB.
What do you mean by "the message size"? SSL doesn't have messages that are
visible outside of the SSL implementation itself.
> Do I need to break this large message up in smaller
On Fri, May 15, 2009 at 05:22:16PM -0400, Animesh Chowdhury wrote:
> ok. That sounds good. But, what I'm seeing is that the SSL client hangs when
> the message size is more than 16KB.
> Do I need to break this large message up in smaller chunks or can I use
> SSL_write to send the whole message in
ok. That sounds good. But, what I'm seeing is that the SSL client hangs when
the message size is more than 16KB.
Do I need to break this large message up in smaller chunks or can I use
SSL_write to send the whole message in one shot?
Thanks.
Animesh
On Fri, May 15, 2009 at 3:50 PM, Kyle Hamilton
No matter what you do, the "maximum fragment length" -- the MTU -- is
going to break all of your communications down into smaller packets.
TLS, in its basic form, is designed to be as close as possible to a
replacement for read() and write() -- you read from the connection,
you write to the connec
On Thu May 14 2009, Animesh Chowdhury wrote:
> Hi,
> I've run into an problem where the data that I need to send to the client is
> more than 16KB. How do I set up the session so that I can do the maximum
> fragment length negotiation ?
> Any example code related to this will be extremely helpful.
Hi,
I've run into an problem where the data that I need to send to the client is
more than 16KB. How do I set up the session so that I can do the maximum
fragment length negotiation ?
Any example code related to this will be extremely helpful.
I'm using openssl0.9.8j .
Also if someone can tell me s
