Changes between Version 2 and Version 3 of MapGuideRfc19

Timestamp:

Mar 7, 2007, 4:12:56 PM (17 years ago)

Author:

brucedechant

Comment:

--

MapGuideRfc19

@@ -23 +23 @@
 == Overview ==
 
-There is currently no mechanism in place to allow older clients to communicate with a newer MapGuide web tier or server and vice versa. 
+**** WORK IN PROGRESS ****
+**** WORK IN PROGRESS ****
+**** WORK IN PROGRESS ****
+**** WORK IN PROGRESS ****
+**** WORK IN PROGRESS ****
+
+There is currently no mechanism in place to allow older clients to communicate with a newer MapGuide web tier or server and vice versa. This needs to be addressed in order to allow easier upgrade paths for end-users.
 
 == Motivation ==
@@ -45 +51 @@
 This solution only helps with newer releases of MapGuide as existing releases will not contain this forwards/backwards compatibility logic. However, the web tier/server will assume that if a CVER is not included in the HTTP operation that it is an older client and to use the oldest supported version of the operation.
 
+The web tier and server must always be the same version because there could be changes to the TCP/IP protocol between them that could cause them to no longer comuunicate. There is already logic in place to identify this i
+
 == Implications ==