[mapguide-internals] Re: Please review RFC 66 (Updated)

[Christine Bao]

Hi Trevor & Kenneth,

     Thank you for your comments. I've added the information in RFC.

Thanks & regards,
Christine


------------------------------



Message: 3

Date: Thu, 25 Jun 2009 17:56:07 -0700

From: Trevor Wekel <trevor.wekel at autodesk.com>

Subject: RE: [mapguide-internals] Please review RFC 66 (Updated)

To: MapGuide Internals Mail List <mapguide-internals at lists.osgeo.org>

Message-ID:

      <D8305E7409B5DB46A9D6219E54E1CF1A2A61F821E3 at ADSK-NAMSG-01.MGDADSK.autodesk.com>



Content-Type: text/plain; charset="us-ascii"



You are correct Kenneth,  the RFC should contain some additional details:



C++ method signature and class name (MgSite?) for the new GetSessionTimeout() API



HTTP method parameters and return value for GETSESSIONTIMEOUT API.



An xml schema snippet describing the changes to WebLayout.



Many of the RFCs already contain this information.  http://trac.osgeo.org/mapguide/wiki/MapGuideRfc10 and http://trac.osgeo.org/mapguide/wiki/MapGuideRfc11 are examples of the required documentation.



Thanks,

Trevor





________________________________________

From: mapguide-internals-bounces at lists.osgeo.org [mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Kenneth Skovhede, GEOGRAF A/S [ks at geograf.dk]

Sent: Thursday, June 25, 2009 12:23 PM

To: MapGuide Internals Mail List

Subject: Re: [mapguide-internals] Please review RFC 66 (Updated)



For the other RFC's there has been a clear description of how the schema

changes would be:

http://trac.osgeo.org/mapguide/wiki/MapGuideRfc50



It seems that RFC 66 suggests a schema change as well?

(EnablePingServer)



Is it required that the RFC details the schema change?



I am satisfied with the RFC otherwise.



Regards, Kenneth Skovhede, GEOGRAF A/S