Changes between Version 1 and Version 2 of MapGuideRfc66


Ignore:
Timestamp:
06/16/09 19:52:47 (16 years ago)
Author:
CXYS
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • MapGuideRfc66

    v1 v2  
    2828== Motivation ==
    2929
    30 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.
    31 The use cases would be:
    32 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.
    33 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.
     30Customer 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]]
     31The use cases would be:[[BR]]
     321.      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]]
     332.      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]]
    34343.      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.
    3535
    3636== Proposed Solution ==
    3737
    38 The possible solutions could be:
    39 1.      Implement a script which pings the servers periodically to keep the both sessions alive (from browser to web extension and from web extension to server).
     38The possible solutions could be:[[BR]]
     391.      Implement a script which pings the servers periodically to keep the both sessions alive (from browser to web extension and from web extension to server). [[BR]]
    40402.      Refine the code handling the "connection broken" exception to provide more friendly messages.
    4141
    4242== Implications ==
    4343
    44 1.      Keep alive
    45 a.      Ajax viewer pings server periodically by calling “GetFeatureProviders” (the most lightweight function).
    46 b.      Fusion viewer pings server periodically by calling Common.php which will refresh connection.
    47 2.      Refine “connection broken” exception handling
     441.      Keep alive[[BR]]
     45a.      Ajax viewer pings server periodically by calling “GetFeatureProviders” (the most lightweight function).[[BR]]
     46b.      Fusion viewer pings server periodically by calling Common.php which will refresh connection.[[BR]]
     472.      Refine “connection broken” exception handling[[BR]]
    4848Catch the exception and show a readable message.
    4949