[reSIProcate] TLS Client Connect Inefficiency

[Derek MacDonald]

I'm going to fix this early next week; Nagendra explained the necessary
openssl details to me.

 

--Derek

 

CONFIDENTIALITY NOTICE

This email and any files transmitted with it contains proprietary
information and, unless expressly stated otherwise, all contents and
attachments are confidential. This email is intended for the addressee(s)
only and access by anyone else is unauthorized. If you are not an addressee,
any disclosure, distribution, printing or copying of the contents of this
email or its attachments, or any action taken in reliance on it, is
unauthorized and may be unlawful. If you are not an addressee, please inform
the sender immediately and then delete this email and any copies of it.
Thank you for your co-operation.

  _____  

From: resiprocate-devel-bounces at list.sipfoundry.org
[mailto:resiprocate-devel-bounces at list.sipfoundry.org] On Behalf Of Scott
Godin
Sent: Tuesday, November 08, 2005 8:20 AM
To: resiprocate
Subject: [reSIProcate] TLS Client Connect Inefficiency

 

I've recently noticed that the TlsConnect code is very CPU aggressive when
forming a TLS connection.  

 

Essentially  - while the connection is being made, there is still a message
on the TxFifo for the TlsTransport - this causes the getNextProcessTimeMs
func to keep returning 0 - until the connection is formed and the message is
sent.  This is a tight loop in the select/process loop.

 

Any thoughts on how to fix this properly? 

 

Scott

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20051114/677c972a/attachment.htm>