SSL Handshake in WebServices

[Rodrigo García]

Hi,
I'm working on an implementation of the TPC-App benchmark, it is very
similiar to the TPC-W benchmark (a number of threads emulating businesses
calling the web services of the server by https).
TPC-APP specifies that a new SSL-Handshake(SSL-Session creation) must be
made in each business session. My question is, as the connections arrive from
the same machine (which is running the threads), do all web service calls
belong to the same SSL-Session?, if they don't, how can I control when
SSL-Sessions are created of closed?.
Note I call the Web Services through the proxy class created by .NET.

Regards,
Rodrigo.

PS. I apologize for my english ;)

[Rodrigo García]

Hi again,

I finally found that a new SSL Session is started when you change the
ConnectionGroupName property in the proxy class (I had to use a sniffer, as
the documentation did not mention anything about SSL), afterwards, all web
service calls made with the same ConnectionGroupName share the same SSL
Session (if in the server side the keep-alive connections are allowed).
Now the problem arises when I want to explicitly close that session, calling
Dispose on the proxy class does not work, changing the MaxIdleTime on the
ServicePoint does not work either and I prefer not to change anything in the
server side IIS.
But when I close the application that makes the web service calls, all
connections close instantly, so I wonder that there has to be a way to close
those connections programatically. Could anybody help me with this?

Regards,
Rodrigo.