[mapguide-internals] Motion: vote RFC 74 - Move or rename resource avoid breaking links

[Trevor Wekel]

+1 Trevor assuming backward compatibility is maintained.

Please note, two method signatures must be implemented to maintain backward compatibility.  Simply adding "bool cascade" to the existing method signature will break backward compatibility.  The only reason I mention it is because of this statement in the implications section:

Implications
After changing this API all the related applications should be updated.

Thanks,
Trevor


-----Original Message-----
From: mapguide-internals-bounces at lists.osgeo.org [mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Tom Fukushima
Sent: July 28, 2009 6:06 PM
To: MapGuide Internals Mail List
Subject: [mapguide-internals] Motion: vote RFC 74 - Move or rename resource avoid breaking links

Hi,

I motion for a vote on

RFC 74 - Move or rename resource avoid breaking links
http://trac.osgeo.org/mapguide/wiki/MapGuideRfc74

+1 Tom

Here is a link to the review discussion: http://n2.nabble.com/Please-review-RFC-74-td3218437.html

Thanks
Tom
_______________________________________________
mapguide-internals mailing list
mapguide-internals at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-internals