<div>
<div>
<span>Hey Olivier,<div><br></div><div>Happy to wait until the next release cycle so you guys can focus on 1.0 :)</div><div><br></div><div>I'll send something through in the next few days (hopefully).</div><div><br></div><div>Cheers,</div><div>Damon.</div></span>
<span><br>-- <br>Damon Oehlman - Co-founder<div>t: DamonOehlman</div><div>p: +61 407 542 009</div><div><br><div>Sidelab Pty Ltd</div><div>http://www.sidelab.com/</div></div></span>
<p style="color: #a0a0a0;">On Monday, 6 June 2011 at 12:38 AM, Olivier Courtin wrote:</p>
<blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;">
<span><div><div><br>On Jun 1, 2011, at 12:51 PM, Damon Oehlman wrote:<br><br>Damon,<br><br>(Sorry for the delay, AFK theses previous days...)<br><br><blockquote type="cite"><div>First I just want to say a big thanks to Olivier for creating <br>TinyOWS. I only came across it last night in a search for a <br>lightweight WFS server, and have been extremely impressed with it.<br><br>We are currently developing a mapping web application for a local <br>client and while we have had Geoserver in the solution stack from <br>the beginning, once we started load testing I felt that we could do <br>better. Coming across the presentation comparing Geoserver, <br>Mapserver and TinyOWS was fantastic and a brilliant introduction to <br>the project.<br><br>While I can't say for certain, I expect that we will replace <br>Geoserver with TinyOWS for our final solution build.<br><br>I have already checked out a readonly version of the repo and <br>started making a few tweaks for features that we need in the project <br>(the case insensitive PropertyIsLike via the matchCase attribute for <br>example). This was very simple, given it had already been <br>implemented for other PropertyIs* tag handling.<br><br>While I'm not a C++ coder (well not for a while now anyway) I'd be <br>happy to submit patch files for review and possible inclusion into <br>TinyOWS. If you can let me know the best way to do this, I'll <br>happily send a patch file through.<br></div></blockquote><br>Few things;<br>- Patch are always welcome, especially when they improve standard <br>compliancy,<br> performance, or security issues.<br><br>- To provide a patch, best way is to modify your own local svn code <br>repository then<br> send the result, as an attachement to the list, of :<br> svn diff<br><br>- Right now we are in 1.0 release cycle, so we could incclude patch <br>only if both:<br> - It's related to WFS 1.1.0 or 1.0.0 mandatory compliancy, or <br>it's a bugfix.<br> - you send them that quickly<br> Otherwise it will be postponed to the next release...<br><br><br>Enjoy using TinyOWS,<br><br>--<br>Olivier<br>_______________________________________________<br>TinyOWS-users mailing list<br><a href="mailto:TinyOWS-users@lists.maptools.org">TinyOWS-users@lists.maptools.org</a><br><a href="http://lists.maptools.org/mailman/listinfo/tinyows-users">http://lists.maptools.org/mailman/listinfo/tinyows-users</a><br></div></div></span>
</blockquote>
<div>
<br>
</div>
</div>
</div>