<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.5730.11" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=416565914-20012007><FONT face=Arial
color=#0000ff size=2>John -</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=416565914-20012007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=416565914-20012007><FONT face=Arial
color=#0000ff size=2>Well, that's OK, but it is not reasonable for the MapServer
community to devote time to an alleged bug that the finder won't report and you
can't replicate. That's not a bug, that's FUD.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=416565914-20012007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=416565914-20012007><FONT face=Arial
color=#0000ff size=2>I can report that I use MapServer in FastCGI mode
extensively without any memory leak problems I'm aware of. And I have done
that over a few releases of MapServer. But like any MapServer user, there
are many features I do *not* use, and it's certainly possible that there are
memory leaks in those features. But making the overly-broad generalization
that "running it in FastCGI mode will eventually cause issues" is incorrect and
uninformative.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=416565914-20012007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=416565914-20012007><FONT face=Arial
color=#0000ff size=2> - Ed</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=416565914-20012007><FONT face=Arial
color=#0000ff size=2><!-- Converted from text/plain format -->
<P><FONT size=2>Ed McNierney<BR>President and Chief Mapmaker<BR>TopoZone.com /
Maps a la carte, Inc.<BR>73 Princeton Street, Suite 305<BR>North Chelmsford,
MA 01863<BR>Phone: +1 (978) 251-4242<BR>Fax: +1 (978)
251-1396<BR>ed@topozone.com</FONT> </P></FONT></SPAN></DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> UMN MapServer Users List
[mailto:MAPSERVER-USERS@LISTS.UMN.EDU] <B>On Behalf Of </B>John
Mitchell<BR><B>Sent:</B> Saturday, January 20, 2007 8:40 AM<BR><B>To:</B>
MAPSERVER-USERS@LISTS.UMN.EDU<BR><B>Subject:</B> Re: [UMN_MAPSERVER-USERS]
MapServer contains some memory leaks whereby running it in FastCGI
mode<BR></FONT><BR></DIV>
<DIV></DIV>Howard,<BR><BR>I can't disclose the below mentioned product. A
few months ago I was told that we were going to use this product for rapid
display of Raster mosaic imagery, and I started to look for alternatives when I
did not get customer support in a timely fashion. I asked the
Community Mapbuilder's developers list for alternatives and MapServer was one of
the possibilities suggested. In my testing of MapServer so far I have been
very impressed with it's flexibility and performance, but the memory leak issue
is the only thing that concerns me at this point. I have not been able to
replicate the memory leak problem, but I wanted to know if any other users have
experienced this problem, and if their is a plan to fix this problem. I
use open source for all my other applications so it makes sense to stick with
MapServer. <BR><BR>Why they are not willing to contribute their fixes back to
the software? I don't know other than to speculate that they want to be
able to justify their high price by their software's uniqueness.<BR><BR>John
<BR><BR><BR>
<DIV><SPAN class=gmail_quote>On 1/16/07, <B class=gmail_sendername>Howard
Butler</B> <<A href="mailto:hobu@iastate.edu">hobu@iastate.edu</A>>
wrote:</SPAN>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">John,<BR><BR>Which
product is xyzGeoServer and why aren't they willing to<BR>contribute their
fixes back to the software?<BR><BR>Howard<BR><BR>At 12:17 PM 1/15/2007, John
Mitchell wrote:<BR>>------=_Part_39643_12109009.1168885022370
<BR>>Content-Type: text/plain; charset=ISO-8859-1;
format=flowed<BR>>Content-Transfer-Encoding:
7bit<BR>>Content-Disposition:
inline<BR>><BR>>Hi,<BR>><BR>>Below is a comment from a developer
of a GeoServer product that runs on top <BR>>of MapServer, which I will
call xyzGeoServer<BR>><BR>>The open source MapServer contains some
memory leaks whereby running it in<BR>>FastCGI mode will eventually cause
issues, however in the xyzGeoServer<BR>>release it handles
properly.<BR>><BR>>Does the above statement have any truth to it or has
recent upgrades to<BR>>MapServer fixed this
issue?<BR>><BR>>Thanks,<BR>><BR>>--<BR>>John J.
Mitchell<BR>><BR>>------=_Part_39643_12109009.1168885022370<BR>>Content-Type:
text/html; charset=ISO-8859-1<BR>>Content-Transfer-Encoding:
7bit<BR>>Content-Disposition:
inline<BR>><BR>>Hi,<br><br>Below is a comment from a
developer of a GeoServer <BR>>product that runs on top of MapServer, which
I will call xyz<span<BR>>style="color: rgb(0, 0, 0);"><font
face="Arial"<BR>>size="2">GeoServer</font></span><br><br><span>
<BR>><font color="#0000ff" face="Arial" size="2">The open
source<BR>>MapServer contains some memory leaks<BR>>whereby running it
in FastCGI mode will eventually cause<BR>>issues,&nbsp;however in
<BR>>the xyzGeoServer release it handles
properly.<br><br><span<BR>>style="color: rgb(0, 0,
0);">Does the above statement have any truth<BR>>to it or has recent
upgrades to MapServer fixed this
<BR>>issue?<br><br>Thanks,<br
clear="all"></span><BR>></font></span><br>--
<br>John J.
Mitchell<BR>><BR>>------=_Part_39643_12109009.1168885022370--<BR><BR></BLOCKQUOTE></DIV><BR><BR
clear=all><BR>-- <BR>John J. Mitchell </BODY></HTML>