[mapguide-internals] missing backward compatibilty of 2.1 server API - feature or defect?

[Zac Spitzer]

I added this as a page to the wiki

http://trac.osgeo.org/mapguide/wiki/VersionCompatibility

z

On Fri, Apr 24, 2009 at 8:53 AM, Steve Dang <steve.dang at autodesk.com> wrote:
> Some notes about MG backward/forward compatibilities:
>
> 1. Old/new web extensions and servers must not be mixed.
> 2. Old clients should work with old/new web extensions and servers.
> 3. New clients will not (always) work with old web extensions and servers.
>
> The problem that UV ran into is probably related to #3.
>
> Steve.
>
> -----Original Message-----
> From: mapguide-internals-bounces at lists.osgeo.org [mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Tom Fukushima
> Sent: Thursday, April 23, 2009 3:51 PM
> To: MapGuide Internals Mail List
> Subject: RE: [mapguide-internals] missing backward compatibilty of 2.1 server API - feature or defect?
>
> Hi,
>
> According to the RFC, everything done in there is backwards compatible.  What's going on? Steve, do you understand the problem that UV is running into?
>
> Tom
>
> -----Original Message-----
> From: mapguide-internals-bounces at lists.osgeo.org [mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Walt Welton-Lair
> Sent: Thursday, April 23, 2009 10:05 AM
> To: MapGuide Internals Mail List
> Subject: RE: [mapguide-internals] missing backward compatibilty of 2.1 server API - feature or defect?
>
> It was changed as part of RFC 53.  I agree - the HTTP request version should have been incremented for the updated APIs.
>
> -----Original Message-----
> From: mapguide-internals-bounces at lists.osgeo.org [mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of UV
> Sent: Thursday, April 23, 2009 11:55 AM
> To: MapGuide Internals Mail List
> Subject: Re: [mapguide-internals] missing backward compatibilty of 2.1 server API - feature or defect?
>
> DESCRIBEFEATURESCHEMA&VERSION=1.0.0
> RESOURCEID=.....
>
> and the parameter count of mapguide studio 2.0.0.3202 is not compatible
> to 2.0.2
> using 2 instead 3 parms i think.
>
> supposedly the maestro client has been updated....
>
> I am simply questioning  why to break it in the first place......
> I believe breaking compatibility in the API between successive versions
> is bad practise......
>
> Jason Birch wrote:
>> Do you know which specific API call was changed, causing the exception?
>>
>> -----Original Message-----
>> From: UV
>> Sent: April-23-09 8:03 AM
>> To: MapGuide Internals Mail List
>> Subject: [mapguide-internals] missing backward compatibilty of 2.1 server API - feature or defect?
>>
>> A recent attempt to verify the map structures used for my test case
>> using Mapguide Studio
>> an access to a  data resource from within a layer triggered an exception
>> in the server.
>> (unable to process operation)(Resource ID does not refer to a valid
>> feature source)
>>
>> This is due to a changed parameter count in the request package.
>> _______________________________________________
>> mapguide-internals mailing list
>> mapguide-internals at lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
>>
>>
>
> _______________________________________________
> mapguide-internals mailing list
> mapguide-internals at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
> _______________________________________________
> mapguide-internals mailing list
> mapguide-internals at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
> _______________________________________________
> mapguide-internals mailing list
> mapguide-internals at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
> _______________________________________________
> mapguide-internals mailing list
> mapguide-internals at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
>



-- 
Zac Spitzer -
http://zacster.blogspot.com
+61 405 847 168