Changes between Version 8 and Version 9 of MapGuideRfc66


Ignore:
Timestamp:
06/25/09 20:07:38 (16 years ago)
Author:
CXYS
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • MapGuideRfc66

    v8 v9  
    40402.      Refine the code handling the exceptions like "connection broken" to provide more friendly messages.
    4141
    42 Detail implementation:[[BR]]
    43 1.      Keep alive[[BR]]
    44    a.   Fusion already pings server periodically by calling "Common.php", so there is no plan to change Fusion's behavior.[[BR]]
     42Detail implementation:
     43
     44
     451.      Keep alive
     46
     47
     48   a.   Fusion already pings server periodically by calling "Common.php", so there is no plan to change Fusion's behavior.
     49
     50
    4551   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]]
    4652     1).  Create a server API GetSessionTimeout(), return the timeout setting from server side. [[BR]]
    … …  
    8490[[BR]]
    8591
    86 
    8792     2).  Call GetSessionTimeout() from mainframe.templ periodically.[[BR]]
    8893MapAgent.fcgi operation sample is:[[BR]]
    … …  
    9196}}}
    9297[[BR]]
    93 
    9498
    9599     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]]