[mapguide-internals] Please review RFC 66

[Chris Claydon]

I thought I saw some code go into Fusion trunk to allow the user to specify a certain amount of map state when loading a layout, so we might be able to do a little better than a full browser refresh. I was thinking more along the lines of re-creating any session-resident resources and preserving as much state information as is available (and applicable) within the client.

I can't claim to have given this any in-depth analysis, however.

Chris.

-----Original Message-----
From: mapguide-internals-bounces at lists.osgeo.org [mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Jason Birch
Sent: Wednesday, June 17, 2009 9:03 AM
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] Please review RFC 66

What would this user prompt look like?

I think that with the current users if your connection is dropped you need a full browser refresh to re-establish your session and all of the objects associated with it.  If that's the case, would the user be told to "press refresh in your browser", or be provided with a button to do the same, or... 

Jason

-----Original Message-----
From: mapguide-internals-bounces at lists.osgeo.org [mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Chris Claydon
Sent: Wednesday, June 17, 2009 7:25 AM
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] Please review RFC 66

I agree that this should be configurable. My preference is to switch it on by default. Fusion already pings the server periodically to keep the session alive, and I think it prevents more problems than it causes. However, it needs to be updated so that if the session no longer exists, it stops trying, and prompts the user to re-connect. - with the current setup, the error log can get filled with "Session not found" errors if the server is re-started (and thus the original session is lost). I'm pretty sure there is already a Trac ticket logged against Fusion for this issue.

Chris.

-----Original Message-----
From: mapguide-internals-bounces at lists.osgeo.org [mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Haris Kurtagic
Sent: Wednesday, June 17, 2009 6:35 AM
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] Please review RFC 66


For Keep alive script there will be option to turn it on or off ?

I don't like idea of clients making constant auto requests to server.
Perhaps for some applications it make sense but I think that should be
optional to turn it on (include script).

Haris

-----Original Message-----
From: mapguide-internals-bounces at lists.osgeo.org
[mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of
Christine Bao
Sent: Wednesday, June 17, 2009 5:12 AM
To: mapguide-internals at lists.osgeo.org
Subject: [mapguide-internals] Please review RFC 66

Hi all,

     RFC 66 -
Failover<https://trac.osgeo.org/mapguide/wiki/MapGuideRfc66> is posted.
Would you please review it? Thank you in advance.

Thanks & regards,
Christine

_______________________________________________
mapguide-internals mailing list
mapguide-internals at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-internals
_______________________________________________
mapguide-internals mailing list
mapguide-internals at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-internals
_______________________________________________
mapguide-internals mailing list
mapguide-internals at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-internals
_______________________________________________
mapguide-internals mailing list
mapguide-internals at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-internals