[mapserver-users] cgi, fastcgi or apache module?

[woodbri at swoodbridge.com]

http://mapserver.gis.umn.edu/cgi-bin/wilma_glimpse/mapserver-
users?query=thread-
safe&Search=Search&partial=on&filelist=0207&filelist=0206&filelist=020
5&filelist=0204&filelist=0203&filelist=0202&filelist=0201&errors=0&max
files=50&maxlines=10&.cgifields=lineonly&.cgifields=filelist&.cgifield
s=case&.cgifields=partial&.cgifields=restricttofiles

On 23 Jul 2002 at 14:05, Bart van den Eijnden wrote:

> Hi Paul,
> 
> thanks for your answer. You refer to something Daniel has noted, what was the exact email in which he noted this?
> 
> And how difficult is it you think to make mapserver thread-safe and where could be the bottle-necks?
> 
> Greetings,
> Bart
> 
> 7/19/2002 6:47:11 PM, Paul Ramsey <pramsey at refractions.net> wrote:
> 
> >I was thinking that an abstracted version of PHP/Mapscript could handle
> >this nicely. PHP already does persistent connections, so some work
> >around allowing PHP/Mapscript to use existing resource allocators to
> >grab the connection objects from the PHP system would allow Mapserver
> >apps to take advantage. PHP can be a great little application server,
> >all the infrastructure is already there. Regardless of whether FastCGI
> >or PHP or a module approach is taken though, the basic thread-safety
> >issues have to be resolved, as Daniel has noted.
> >
> >P.
> >
> >Bart van den Eijnden wrote:
> >> 
> >> Hi list,
> >> did anybody ever think about changing mapserver from a cgi to a fastcgi, or to an Apache module? If not what where the reasons?
> >> This particularly for using mapserver on Oracle Spatial so you can keep the connection open.
> >> 
> >> Greetings,
> >> Bart
> >> The Netherlands
> >
> >-- 
> >      __
> >     /
> >     | Paul Ramsey
> >     | Refractions Research
> >     | Email: pramsey at refractions.net
> >     | Phone: (250) 885-0632
> >     \_
> >
> 
> 
> 
>