Changes between Version 8 and Version 9 of MapGuideRfc66

Timestamp:

Jun 25, 2009, 8:07:38 PM (15 years ago)

Author:

CXYS

Comment:

--

MapGuideRfc66

@@ -40 +40 @@
 2.      Refine the code handling the exceptions like "connection broken" to provide more friendly messages.
 
-Detail implementation:[[BR]]
-1.      Keep alive[[BR]]
-   a.   Fusion already pings server periodically by calling "Common.php", so there is no plan to change Fusion's behavior.[[BR]]
+Detail implementation:
+
+
+1.      Keep alive
+
+
+   a.   Fusion already pings server periodically by calling "Common.php", so there is no plan to change Fusion's behavior.
+
+
    b.   Ajax viewer doesn’t ping server to keep-alive so far. If open an Ajax viewer and leave it open for a while more than the timeout interval, it can’t continue work. To keep Ajax viewer alive, the approach is:[[BR]]
      1).  Create a server API GetSessionTimeout(), return the timeout setting from server side. [[BR]]
@@ -84 +90 @@
 [[BR]]
 
-
      2).  Call GetSessionTimeout() from mainframe.templ periodically.[[BR]]
 MapAgent.fcgi operation sample is:[[BR]]
@@ -91 +96 @@
 }}}
 [[BR]]
-
 
      3).  User doesn’t need to set the time interval of pinging. It’s read from server timeout setting and divided by 5. User can turn the ping on/off by setting <EnablePingServer>=1/0 of basic web layout. [[BR]]