[mapguide-trac] #972: Failing operation when accessing 2.1 server with 2.0 client

[MapGuide Open Source]

#972: Failing operation when accessing 2.1 server with 2.0 client
---------------------------+------------------------------------------------
 Reporter:  uvlite         |         Owner:       
     Type:  defect         |        Status:  new  
 Priority:  low            |     Milestone:       
Component:  Server         |       Version:  2.1.0
 Severity:  minor          |    Resolution:       
 Keywords:  compatibility  |   External_id:       
---------------------------+------------------------------------------------
Comment (by uvlite):

 I see. But the simple statement that we cannot mix the two says it all.

 This is a good example of implicit expert knowledge which is required to
 use this system.

 Robust design would require:
 '''The system has to know what its dealing with. '''

 The fact that I can have different versions running on different nodes and
 no part of the systen notices the problem is a minor but still a defect
 from my understanding of system design.


 There is a simple solution.

 Many other systems use a unique identifier to identify serialized objects.
 In my experience (taking into account a limited insight into details by
 many engineers involved in using and handling such a system)
 this leads to problems as the one I have described.

 The most simple way to handle this is to exchange version numbers in the
 create session operation.  [[BR]]

-- 
Ticket URL: <http://trac.osgeo.org/mapguide/ticket/972#comment:3>
MapGuide Open Source <http://mapguide.osgeo.org/>
MapGuide Open Source Internals