RE: [twsocket] Is there a way to download a file in threads?

2005-04-14 Thread Bjørnar Nielsen
 

 The only shortcoming of ICS is the web server which has no official and/or
optimized CGI/ISAPI
 component and by design async which is bad for a web server. 

SZ, why do you think async design is bad for a webserver?

Regards Bjørnar



--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be


Re: [twsocket] Is there a way to download a file in threads?

2005-04-14 Thread Fastream Technologies
Hello,
Well, async cannot take advantage of multi-processor systems. Also for CGI 
and ISAPI execution, threads seem to be a better way. And all the commercial 
Web servers I know such as IIS and Apache chose it for these reasons.

Best Regards,
SZ
- Original Message - 
From: Bjrnar Nielsen [EMAIL PROTECTED]
To: 'ICS support mailing' twsocket@elists.org
Sent: Thursday, April 14, 2005 10:38 AM
Subject: RE: [twsocket] Is there a way to download a file in threads?



The only shortcoming of ICS is the web server which has no official and/or
optimized CGI/ISAPI
component and by design async which is bad for a web server.
SZ, why do you think async design is bad for a webserver?
Regards Bjrnar

--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be 

--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be


RE: [twsocket] Is there a way to download a file in threads?

2005-04-14 Thread Primož Gabrijelčič
 Well, async cannot take advantage of multi-processor systems. 
 Also for CGI and ISAPI execution, threads seem to be a better 
 way. And all the commercial Web servers I know such as IIS 
 and Apache chose it for these reasons.

You are mixing up two factors.

Even on multi-processor system, one CPU is usually enough to handle
connections.  That doesn't prevent you from creating additional threads to
process CGI and ISAPI requests - nobody says that such requests must execute
in the context of the thread handling socket connections.

One of my commercial designs is using this approach and it is working just
great.

Best regards,
Primoz


-- 
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be