<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"\@SimSun";
panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri","sans-serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:247078902;
mso-list-type:hybrid;
mso-list-template-ids:-1511110660 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoPlainText">Hi Greg, <o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">After careful think, I found it's very hard to do the same thing for managed FDO API. I guess you already know this so that's why you bring this question. Thank you.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Let me explain what I understand. Please correct me if any mistake.
<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Assume I create a managed API for FdoCoordinateSystemTransform, naming mgFdoCoordinateSystemTransform, which implement the function
<o:p></o:p></p>
<p class="MsoPlainText"> virtual FdoIDirectPosition* CoordinateSystemTransform(FdoIDirectPosition* sourceGeometry);<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">However in FDO managed API, only the native FdoXmlFeatureFlags* GetImpObj() is used, so only the native FdoCoordinateSystemTransform can be used. The override CoordinateSystemTransform(...) function has no chance to get called.
<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">I suggest we ignore this coordinate system transformation function in managed API, because:<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 lfo1">
<![if !supportLists]><span style="mso-list:Ignore">1.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>It’s not mandatory for managed API. It’s an optional enhanced function but not must-have. Without it managed FDO API works well.
<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:.5in">This function is necessary for MapGuide WFS creation, but we don’t have use case for managed FDO yet. If the native FDO cannot make this change, the serialize code have to be copied to MapGuide and they are duplicated.<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 lfo1">
<![if !supportLists]><span style="mso-list:Ignore">2.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>Managed FDO API has been inconsistent in other functions. For example, XmlFeatureFlags miss the following functions already.<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 lfo1">
<![if !supportLists]><span style="mso-list:Ignore">a.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>Get/SetDefaultNamespacePrefix<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 lfo1">
<![if !supportLists]><span style="mso-list:Ignore">b.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>Get/SetGmlIDRelatePropertyNames<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 lfo1">
<![if !supportLists]><span style="mso-list:Ignore">c.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>Get/SetGmlNameRelatePropertyName<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 lfo1">
<![if !supportLists]><span style="mso-list:Ignore">d.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>Get/SetGmlDescriptionRelatePropertyName<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:.5in">If you would like to have them fixed, I can log a ticket for that.
<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Please let me know your decision. I will update RFC later.
<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Thanks & regards,<o:p></o:p></p>
<p class="MsoPlainText">Christine<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">-----Original Message-----<br>
From: fdo-internals-bounces@lists.osgeo.org [mailto:fdo-internals-bounces@lists.osgeo.org] On Behalf Of Greg Boone<br>
Sent: Friday, April 26, 2013 12:27 AM<br>
To: FDO Internals Mail List<br>
Subject: Re: [fdo-internals] Please review RFC 66</p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Can you include the detailed design of the managed API in the RFC?
<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Specifically, I am interested to know if a client specific implementation of FdoCoordinateSystemTransform interface can be a managed implementation. If that is a possibility, how will the managed to unmanaged translation occur?
<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Regards,<o:p></o:p></p>
<p class="MsoPlainText">Greg<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">-----Original Message-----<o:p></o:p></p>
<p class="MsoPlainText">From: fdo-internals-bounces@lists.osgeo.org [mailto:fdo-internals-bounces@lists.osgeo.org] On Behalf Of Christine Bao<o:p></o:p></p>
<p class="MsoPlainText">Sent: Wednesday, April 24, 2013 9:59 PM<o:p></o:p></p>
<p class="MsoPlainText">To: FDO Internals Mail List<o:p></o:p></p>
<p class="MsoPlainText">Subject: Re: [fdo-internals] Please review RFC 66<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Thanks Greg for pointing it out. Yes, I will update the managed FDO API also. I updated the RFC to include this.
<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Thanks & regards,<o:p></o:p></p>
<p class="MsoPlainText">Christine<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">-----Original Message-----<o:p></o:p></p>
<p class="MsoPlainText">From: fdo-internals-bounces@lists.osgeo.org [mailto:fdo-internals-bounces@lists.osgeo.org] On Behalf Of Greg Boone<o:p></o:p></p>
<p class="MsoPlainText">Sent: Wednesday, April 24, 2013 9:59 PM<o:p></o:p></p>
<p class="MsoPlainText">To: FDO Internals Mail List<o:p></o:p></p>
<p class="MsoPlainText">Subject: Re: [fdo-internals] Please review RFC 66<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">One question...<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">What about the Managed FDO API? <o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">public ref class XmlFeatureSerializer sealed<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"> ...\Fdo\Managed\Src\OSGeo\FDO\Xml\mgXmlFeatureSerializer.h<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">public ref class XmlFeatureFlags : public NAMESPACE_OSGEO_FDO_XML::XmlFlags<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"> ...\Fdo\Managed\Src\OSGeo\FDO\Xml\mgXmlFeatureFlags.h<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Greg<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">-----Original Message-----<o:p></o:p></p>
<p class="MsoPlainText">From: fdo-internals-bounces@lists.osgeo.org [mailto:fdo-internals-bounces@lists.osgeo.org] On Behalf Of Jackie Ng<o:p></o:p></p>
<p class="MsoPlainText">Sent: Tuesday, April 23, 2013 10:27 PM<o:p></o:p></p>
<p class="MsoPlainText">To: fdo-internals@lists.osgeo.org<o:p></o:p></p>
<p class="MsoPlainText">Subject: Re: [fdo-internals] Please review RFC 66<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">No problems from me.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">+1 Jackie<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">--<o:p></o:p></p>
<p class="MsoPlainText">View this message in context: <a href="http://osgeo-org.1560.x6.nabble.com/Please-review-RFC-66-tp5048641p5049256.html">
<span style="color:windowtext;text-decoration:none">http://osgeo-org.1560.x6.nabble.com/Please-review-RFC-66-tp5048641p5049256.html</span></a><o:p></o:p></p>
<p class="MsoPlainText">Sent from the FDO Internals mailing list archive at Nabble.com.<o:p></o:p></p>
<p class="MsoPlainText">_______________________________________________<o:p></o:p></p>
<p class="MsoPlainText">fdo-internals mailing list<o:p></o:p></p>
<p class="MsoPlainText"><a href="mailto:fdo-internals@lists.osgeo.org"><span style="color:windowtext;text-decoration:none">fdo-internals@lists.osgeo.org</span></a><o:p></o:p></p>
<p class="MsoPlainText"><a href="http://lists.osgeo.org/mailman/listinfo/fdo-internals"><span style="color:windowtext;text-decoration:none">http://lists.osgeo.org/mailman/listinfo/fdo-internals</span></a><o:p></o:p></p>
<p class="MsoPlainText">_______________________________________________<o:p></o:p></p>
<p class="MsoPlainText">fdo-internals mailing list<o:p></o:p></p>
<p class="MsoPlainText"><a href="mailto:fdo-internals@lists.osgeo.org"><span style="color:windowtext;text-decoration:none">fdo-internals@lists.osgeo.org</span></a><o:p></o:p></p>
<p class="MsoPlainText"><a href="http://lists.osgeo.org/mailman/listinfo/fdo-internals"><span style="color:windowtext;text-decoration:none">http://lists.osgeo.org/mailman/listinfo/fdo-internals</span></a><o:p></o:p></p>
<p class="MsoPlainText">_______________________________________________<o:p></o:p></p>
<p class="MsoPlainText">fdo-internals mailing list<o:p></o:p></p>
<p class="MsoPlainText"><a href="mailto:fdo-internals@lists.osgeo.org"><span style="color:windowtext;text-decoration:none">fdo-internals@lists.osgeo.org</span></a><o:p></o:p></p>
<p class="MsoPlainText"><a href="http://lists.osgeo.org/mailman/listinfo/fdo-internals"><span style="color:windowtext;text-decoration:none">http://lists.osgeo.org/mailman/listinfo/fdo-internals</span></a><o:p></o:p></p>
<p class="MsoPlainText">_______________________________________________<o:p></o:p></p>
<p class="MsoPlainText">fdo-internals mailing list<o:p></o:p></p>
<p class="MsoPlainText"><a href="mailto:fdo-internals@lists.osgeo.org"><span style="color:windowtext;text-decoration:none">fdo-internals@lists.osgeo.org</span></a><o:p></o:p></p>
<p class="MsoPlainText"><a href="http://lists.osgeo.org/mailman/listinfo/fdo-internals"><span style="color:windowtext;text-decoration:none">http://lists.osgeo.org/mailman/listinfo/fdo-internals</span></a><o:p></o:p></p>
</div>
</body>
</html>