Team,
My story with Apache::ASP
I had created an application (consisting of serveral dlls written in VB). I had
naturally been forced to use IIS which lets you call DLLs from ASP.
All I had in the ASP file was a Server.CreateObject("Class.clsClass") which returned
HTML. All the processing and business logic sat within DLLs. I know this does not
confirm to a true ASP deployment (but I really liked using the VB IDE...:) and the
debugging advantages there....)
I was frustrated with having to use IIS, especially when there is no IIS Out of the
box with Win XP. So I find Apache::ASP very useful! I can run my server app on XP,
Win2K, NT ...
I do have a question though. The RAM footprint for Apache has gone up from 3600
KB(Apache by itself) to 56000 KB now(with mod_perl and Apache::ASP). Why is this? Is
this normal behaviour?
Is there a list of modules that absolutely have to be there for Apache::ASP to work?
Maybe I have more modules than needed.
Sorry for the long-winded story (but I truly appreciate Apache::ASP)
Thanks again!
__________________________________________________________________
The NEW Netscape 7.0 browser is now available. Upgrade now!
http://channels.netscape.com/ns/browsers/download.jsp
Get your own FREE, personal Netscape Mail account today at http://webmail.netscape.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
