Hi Daniel,<br><br>Yes, it's not that easy to find the right term ;-) I don't object replacing combine to union if it reflects the functionality in a better way. <br><br>I'm about to finish my testings and call for a vote on this RFC tomorrow. Let me know if anyone has a better term (set's say we go with union right now) or some other idea which I should also incorporate in <a href="http://mapserver.org/trunk/development/rfc/ms-rfc-68.html">RFC 68</a>.<br>
<br>Best regards,<br><br>Tamas<br><br><br><br><div class="gmail_quote">2011/2/24 Daniel Morissette <span dir="ltr"><<a href="mailto:dmorissette@mapgears.com">dmorissette@mapgears.com</a>></span><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Hi Tamas,<br>
<br>
I really like the current version of RFC-68. This is a feature that I wish we had implemented a while ago.<br>
<br>
Just one quick question on terminology, why did you choose to use "CONNECTIONTYPE COMBINE" instead of possibly "CONNECTIONTYPE UNION"?<br>
I'm asking this since the term "combine" led to confusion in the initial RFC-68 discussions a few weeks ago and the term "union" seemed better for everyone. Perhaps Jeff and other people closer to the users can comment on the best term to use?<br>
<br>
Daniel<div class="im"><br>
<br>
<br>
On 11-02-19 05:45 PM, Tamas Szekeres wrote:<br>
</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="im">
Dear PSC,<br>
<br>
Thanks for all who provided feedback to the initial version of MS RFC 68<br></div>
<<a href="http://mapserver.org/development/rfc/ms-rfc-68.html" target="_blank">http://mapserver.org/development/rfc/ms-rfc-68.html</a>>. I've now modified<div class="im"><br>
the concept in some way, which yields a more straightforward solution to<br>
the requirements. I've created two RFCs instead of one by separating the<br>
combination and the clustering option as 2 distinct problems which could<br>
in fact be implemented separately. The clustering stuff has been<br>
stripped from MS RFC 68<br></div>
<<a href="http://mapserver.org/development/rfc/ms-rfc-68.html" target="_blank">http://mapserver.org/development/rfc/ms-rfc-68.html</a>>.<div class="im"><br>
I've also added a working implementation of this the new data provider<br>
to the corresponding ticket<br></div>
<<a href="http://trac.osgeo.org/mapserver/ticket/3674" target="_blank">http://trac.osgeo.org/mapserver/ticket/3674</a>>, see mapcombine.c<br>
<<a href="http://trac.osgeo.org/mapserver/attachment/ticket/3674/mapcombine.c" target="_blank">http://trac.osgeo.org/mapserver/attachment/ticket/3674/mapcombine.c</a>><div class="im"><br>
for the details.<br>
<br>
Let me know if you find further issues related to this concept. If no<br>
singnificant problems encountered I'll motion to adopt this probably in<br>
the next week.<br>
<br>
Best regards,<br>
<br>
Tamas<br>
<br>
<br>
<br>
<br></div>
_______________________________________________<br>
mapserver-dev mailing list<br>
<a href="mailto:mapserver-dev@lists.osgeo.org" target="_blank">mapserver-dev@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/mapserver-dev" target="_blank">http://lists.osgeo.org/mailman/listinfo/mapserver-dev</a><br>
</blockquote>
<br>
<br>
-- <br>
Daniel Morissette<br>
<a href="http://www.mapgears.com/" target="_blank">http://www.mapgears.com/</a><br>
_______________________________________________<br>
mapserver-dev mailing list<br>
<a href="mailto:mapserver-dev@lists.osgeo.org" target="_blank">mapserver-dev@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/mapserver-dev" target="_blank">http://lists.osgeo.org/mailman/listinfo/mapserver-dev</a><br>
</blockquote></div><br><div style="visibility: hidden; left: -5000px; position: absolute; z-index: 9999; padding: 0px; margin-left: 0px; margin-top: 0px; overflow: hidden; word-wrap: break-word; color: black; font-size: 10px; text-align: left; line-height: 130%;" id="avg_ls_inline_popup">
</div>