Thanks for the below, cheers.
 
I indent to have a database pool of about 30 handles ,  and when needed, will grap a free one, use it, then mark it as free again.  All the server app. will be doing is, reading the database records, and creating an HTML, and sending it back, not file transfer needed.
 
I also writing code for a socket IOCP application (run on a different computer), and have created working threads for connection requests. But, I noticed that the ISAPI don't do this (I am new to ISAPI as you have guessed). How does the ISAPI manage many connections?
 
Regards
Neil
 
----- Original Message -----
From: /dev/null
Sent: Thursday, November 17, 2005 5:25 AM
Subject: Re: [msvc] ISAPI programming

Well, it's windows. (I know, "what kind of answer is that?")
 
On a linux system that I maintain we have several hundred connections per second and there isn't any problem. Of course, that's linux/apache.
 
The overhead you will be fighting won't be mfc or isapi dlls. It will be the windows tcp stack, the windows kernel, and IIS.
 
I think you'll be OK, the biggest thing you have going in your favor is you are writing C/C++ code which will compile to be pretty fast.
 
There are some write mechanisms that you may be able to take advantage of if you are sending back files. You can basically end your handling of a connection by calling a "SendFile" type of function (forgot the name, it's been about 4-5 years) that will transmit the specified file using the fastest IO mechanism in windows.
 
Whatever you write, write a "shim" class that your mfc isapi calls into and that whenever your code needs any information about the connection, the user, the server, etc, it calls that same shim class to get it. Also, any data storage format that you use, make it generic, like flat files.
 
If you run into a problem and IIS isn't fast enough we can take that shim and re-write it for receiving calls from apache and getting information from apache about the server, user, connection, etc. and all the rest of your code can stay the same. Then we just compile it as an apache module and you can uninstall that virus from your dual p4 and put linux/apache on there and run with that.
 
I've wrote a couple of apache modules since doing the isapi stuff and will be happy to help you out in the area.
 
----- Original Message -----
From: Neil
Sent: Friday, November 11, 2005 9:22 PM
Subject: Re: [msvc] ISAPI programming

Thanks for your reply, cheers.
 
Can it handle hundreds of connections at a time? We are planning to use P4 dual precessors, 1GB ram, XP or 2000 server
 
Neil
----- Original Message -----
From: /dev/null
Sent: Saturday, November 12, 2005 1:10 AM
Subject: Re: [msvc] ISAPI programming

I used mfc without a problem.
 
everything was fine. I used the mfc classes to do the hooks and filters and then called into my own code to do my own stuff.
----- Original Message -----
From: Neil
Sent: Friday, November 11, 2005 4:36 PM
Subject: Re: [msvc] ISAPI programming

Hi,
did you use MFC? or do you advice to stay away from using it?
 
Neil
----- Original Message -----
From: /dev/null
Sent: Friday, November 11, 2005 10:15 PM
Subject: Re: [msvc] ISAPI programming

I wrote quite a bit of isapi back 6 years ago and never ran into any significant problems. it always did exactly what I wanted and needed it to do.
----- Original Message -----
From: Neil
To: NDThrd
Sent: Friday, November 11, 2005 2:50 AM
Subject: [msvc] ISAPI programming

Hi,
   I am about to start writing  an ISAPI project. I am going to be using MFC , and the book I am using mentions that there are some problems with MFC. The book is quite old, and dont know if the problems have been solved in XP and 2000. 
 
I am using VC++ 6.0, can anyone give me any good tips and  problems they have come across ?
 
Many thanks
Neil


_______________________________________________
msvc mailing list
[email protected]
See http://beginthread.com/mailman/listinfo/msvc_beginthread.com for subscription changes, and list archive.


_______________________________________________
msvc mailing list
[email protected]
See http://beginthread.com/mailman/listinfo/msvc_beginthread.com for subscription changes, and list archive.


_______________________________________________
msvc mailing list
[email protected]
See http://beginthread.com/mailman/listinfo/msvc_beginthread.com for subscription changes, and list archive.


_______________________________________________
msvc mailing list
[email protected]
See http://beginthread.com/mailman/listinfo/msvc_beginthread.com for subscription changes, and list archive.


_______________________________________________
msvc mailing list
[email protected]
See http://beginthread.com/mailman/listinfo/msvc_beginthread.com for subscription changes, and list archive.


_______________________________________________
msvc mailing list
[email protected]
See http://beginthread.com/mailman/listinfo/msvc_beginthread.com for subscription changes, and list archive.
_______________________________________________
msvc mailing list
[email protected]
See http://beginthread.com/mailman/listinfo/msvc_beginthread.com for 
subscription changes, and list archive.

Reply via email to