>Robert Brenstein wrote: >> >> I am moving a few web server projects to MC (from HC). They provide 3 >> independent cgi functions (things like access to a database or >> controlled access to downloadable files) but they can share many >> utilitiy functions (scripts). This will be a Mac-only solution. I >> have thought about three approaches but can't make up my mind which >> is the optimal. >> >> 1. a single MC-based CGI that does all -- a post parameter tells >> which function is called; nice integration and a single server app >> but more complex (troublesome) maintenance and development and >> potential performance issue when all functions are called by many >> users. >> >> 2. a separate MC program for each -- nice independence but the common >> functions have to be replicated (a potential headache for >> maintenance) plus three programs not one competing for cpu cycles >> >> 3. as 2 but the common functions are in a shared stack accessed thru >> "start using". >> >> A forth option would be to use MC as an HTTP server rather than a >> CGI. Unfortunately, my prelim tetsts with MC 2.3.2 and the Infuser >> Example stack (HTTP server kindly provided by another MCer) showed >> that there are consistent problems when using POST from certain >> browsers. > >If you need a server just for cgis your best bet is the last option >considering you modify the MC server to suit you purposes (probably more >consistent headers handling). > >Andu
Do you mean 3 or 4 as the last option? I do not consider 4 as a serious option now, because the http service must be rock solid and I have no time to fiddle with http functionality in MC while I have ready-to-use software for that. Of course, if you guys tell me that MC 2.4 is a ready-to-use, full-service, reliable http server I may reconsider :) The cgi functions are just supplementary. I am running MacHTTP to provide the basic web service. CGI's ran so far on separate computer, but I just got a G4 Mac so I am moving all onto this machine and adding extensive support for database functions (using Valentina). I should add that some POSTs can send substantial amounts of text and the database access will involve a multitude of forms that modify database entries and produce web pages from the database info on the fly. Robert Archives: http://www.mail-archive.com/[email protected]/ Info: http://www.xworlds.com/metacard/mailinglist.htm Please send bug reports to <[EMAIL PROTECTED]>, not this list.
