[mapguide-trac] #1026: Prevent session timeout, and give better error messages (RFC 66)

[MapGuide Open Source]

#1026: Prevent session timeout, and give better error messages (RFC 66)
-----------------------+----------------------------------------------------
   Reporter:  CXYS     |       Owner:  Tom Fukushima
       Type:  defect   |      Status:  new          
   Priority:  medium   |   Milestone:  2.2          
  Component:  General  |     Version:  2.0.2        
   Severity:  major    |    Keywords:               
External_id:           |  
-----------------------+----------------------------------------------------
 Customer reports that if leave the browser open for some while without any
 operation, the session will timeout and can’t get informed. If server is
 down the error message is not easy to read and user can’t figure out what
 happens.[[BR]]
 The use cases would be:[[BR]]
 1. If the Http session is timeout, the user should be informed about the
 fact instead of getting some script errors or meaningless error
 messages.[[BR]]
 2. If the MapGuide Server session is timeout, the user should be informed
 about the fact instead of getting some script errors or some meaningless
 error messages.[[BR]]
 3. If the connection to MapGuide Server is broken, the user should be
 informed by a friendly message which helps the user know what's happening
 instead of getting a kind of "exception stack trace" message box.


 The possible solutions could be:[[BR]]
 1. To avoid timeout (either from browser to web tier, or from web tier to
 MapGuide server), implement a script which pings the servers periodically
 to keep the both sessions alive. [[BR]]
 2. Refine the code handling the exceptions like "connection broken" to
 provide more friendly messages. [[BR]]

 For the detail implementation please see RFC 66.

-- 
Ticket URL: <https://trac.osgeo.org/mapguide/ticket/1026>
MapGuide Open Source <http://mapguide.osgeo.org/>
MapGuide Open Source Internals