I told Christine that we use 1.0.0 for new APIs. Sorry Christine if I was wrong!
-----Original Message-----
From:
[hidden email] [mailto:
[hidden email]] On Behalf Of Trevor Wekel
Sent: Wednesday, August 12, 2009 10:28 PM
To: MapGuide Internals Mail List
Subject: [mapguide-internals] RE: Review FixOperationVersion.patch
Hi Christine,
Please check with Bruce on the operation version convention.
As far as I know, we were using the MapGuide version for any newly introduced operation versions. This means a 1.0.0 operation version is supported in MapGuide version 1.0.0 or later. A 2.2.0 operation is supported in MapGuide 2.2.0 or later.
If a new version of an operation is introduced in MapGuide 2.2.0, then the new operation version should be set to 2.2.0.
If I am correct about the convention, this patch is not required.
Thanks,
Trevor
-----Original Message-----
From:
[hidden email] [mailto:
[hidden email]] On Behalf Of Christine Bao
Sent: August 12, 2009 1:31 AM
To:
[hidden email]
Subject: [mapguide-internals] Review FixOperationVersion.patch
Hi all,
A patch
http://trac.osgeo.org/mapguide/attachment/ticket/1026/FixOperationVersion.patch is attached for ticket
http://trac.osgeo.org/mapguide/ticket/1026. Would you please review it? Thank you.
The comment for this submission:
The operation version should be 1.0.0 for new added API, and it has nothing to do with MapGuide version. This patch fixed the API GetSessionTimeout()'s version from 2.2.0 to 1.0.0.
Thanks & regards,
Christine
_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals
