|
|||||||||
|
|||||||||
| |||||||||
|
|
|
| |||||||||
 |
|
|
«
Previous Thread
|
Next Thread
»
|
Thread Tools | Search this Thread | Rate Thread | Display Modes |
Dev Shed Forums Sponsor:
|
|
|
|
#1
May 2nd, 2007, 03:26 AM
|
|||
|
|||
|
IIS 6.0 & WS & HTTP Keep Alive
Hi,
I have a web service application at the backend and a driver at the front end. The driver consums the web service over SSL. I want to tune up my IIS server machine, so here are the configurations that I defined: Request Queue Length = 300 Connection Timeout = 1 sec HTTP Keep Alive = true ... Normally, if the IIS hosts a web service, the HTTP Keep Alive is not needed; however we run the web service over SSL. So, from my understanding there are two round trips from the driver to the IIS for each request. Is that true? Does it depend on the user mode / kernel mode we use with the SSL? Thanks 
|
|
#2
May 2nd, 2007, 11:30 PM
|
|||
|
|||
|
Why not use Ethereal (or whatever it's become now) and inspect the actual packets? Otherwise, I don't know the answer, perhaps others will be able to help.
__________________
====== Doug G ====== I didn't attend the funeral, but I sent a nice letter saying I approved of it. --Mark Twain
|
|
| Viewing: Dev Shed Forums > System Administration > IIS > IIS 6.0 & WS & HTTP Keep Alive |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|
 |
|
|
Del.icio.us
Digg
Google
Spurl
Blink
Furl
Simpy
Y! MyWeb
Linear Mode
