Changes between Version 5 and Version 6 of MapGuideRfc19

Timestamp:

Mar 8, 2007, 1:21:55 PM (17 years ago)

Author:

brucedechant

Comment:

--

MapGuideRfc19

@@ -27 +27 @@
 == Motivation ==
 
-There needs to be a way for a client to be able to identify the version it is so that the web tier and server can properly communicate with it. By knowing the client version the web tier and server will be able to process the appropriate operation version and use the appropriate schema version. This will allow the web tier and server to server both old and new clients and for new clients to connect to an older web tier and server. This proposal hopes to add some form of forwards/backwards compatibility to !MapGuide in order to solve this.
+There needs to be a way for a client to be able to identify the version it is so that the web tier and server can properly communicate with it. By knowing the client version the web tier and server will be able to process the appropriate operation version and use the appropriate schema version. This will allow the web tier and server to serve both old and new clients and for new clients to connect to an older web tier and server. This proposal hopes to add some form of forwards/backwards compatibility to !MapGuide in order to solve this.
 
 == Proposed Solution ==
@@ -33 +33 @@
 A new HTTP parameter "CVER" needs to be added to all HTTP requests. This new parameter will be used to identify the client version.
 The new HTTP parameter has the following format:
-
-!MajorVersion.!MinorVersion
+{{{
+CVER=MajorVersion.MinorVersion
 
 Example:
 
 CVER=1.2
+}}}
 
 The web tier and server will be able to use this information in order to do the operation that supports the specified client version. This will allow schema changes to take place and for multiple versions of the schema to be supported because the client tells us what version it is and therefore what schema version it supports.