Please take a look at this pull request:
https://github.com/joyent/node/pull/3661

If it'll get landed into node's core - you'll be able to control session
storage manually from js land.

Cheers,
Fedor.



On Sun, Aug 26, 2012 at 1:38 AM, Mark Hahn <[email protected]> wrote:

> What is the "convincing use case"?
>
>
> On Sat, Aug 25, 2012 at 11:18 AM, Satyam Shekhar 
> <[email protected]>wrote:
>
>> Hi,
>>
>> On Sat, Aug 25, 2012 at 5:22 PM, Ben Noordhuis <[email protected]>wrote:
>>
>>> On Sat, Aug 25, 2012 at 10:52 AM, Chaitanya Gupta
>>> <[email protected]> wrote:
>>> > I need to support TLS session resumption in my node.js app. I am
>>> > creating a TLS server usingrequire('tls').createServer(). By default,
>>> > the server has a session ticket lifetime of 300 seconds (as seen with
>>> > OpenSSL's s_client).
>>> >
>>> > I need the session timeout to be beyond 300 seconds. How can I do
>>> > this? I couldn't find anything in node's API docs that could help.
>>>
>>> Node doesn't let you do that. If you have a convincing use case,
>>> please open an issue and we'll add it.
>>
>>
>>
>> I want to contribute this.
>>
>> I was thinking of implementing it in one of the following ways -
>>
>> 1.
>> i) Take sessionTimeout as an option to createServer
>> ii) Expose a method setTimeout on SecureContext in node_crypto.cc which
>> calls SSL_CTX_set_timeout, and use that to set default session timeout for
>> the context, from the "connection" event callback inside createServer.
>>
>> 2.
>> i) Expose setSessionTimeout on CryptoStream in tls.js which again calls
>> setSessionTimeout exposed by Connection in node_crypto.cc. This
>> calls SSL_SESSION_set_timeout to set the timeout for that session. Now, the
>> user can call setSessionTimeout on the exposed CleartextStream to set the
>> timeout.
>>
>> What do you think?
>>
>> -- satyam
>>
>>
>>>
>>> --
>>> Job Board: http://jobs.nodejs.org/
>>> Posting guidelines:
>>> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
>>> You received this message because you are subscribed to the Google
>>> Groups "nodejs" group.
>>> To post to this group, send email to [email protected]
>>> To unsubscribe from this group, send email to
>>> [email protected]
>>> For more options, visit this group at
>>> http://groups.google.com/group/nodejs?hl=en?hl=en
>>>
>>
>>  --
>> Job Board: http://jobs.nodejs.org/
>> Posting guidelines:
>> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
>> You received this message because you are subscribed to the Google
>> Groups "nodejs" group.
>> To post to this group, send email to [email protected]
>> To unsubscribe from this group, send email to
>> [email protected]
>> For more options, visit this group at
>> http://groups.google.com/group/nodejs?hl=en?hl=en
>>
>
>  --
> Job Board: http://jobs.nodejs.org/
> Posting guidelines:
> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
> You received this message because you are subscribed to the Google
> Groups "nodejs" group.
> To post to this group, send email to [email protected]
> To unsubscribe from this group, send email to
> [email protected]
> For more options, visit this group at
> http://groups.google.com/group/nodejs?hl=en?hl=en
>

-- 
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

Reply via email to