[fdo-internals] Please review RFC 66

[Christine Bao]

Hi Greg,



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.



Let me explain what I understand. Please correct me if any mistake.



Assume I create a managed API for FdoCoordinateSystemTransform, naming mgFdoCoordinateSystemTransform, which implement the function

                virtual FdoIDirectPosition* CoordinateSystemTransform(FdoIDirectPosition* sourceGeometry);



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.



I suggest we ignore this coordinate system transformation function in managed API, because:

1.       It's not mandatory for managed API. It's an optional enhanced function but not must-have. Without it managed FDO API works well.

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.

2.       Managed FDO API has been inconsistent in other functions. For example, XmlFeatureFlags miss the following functions already.

a.       Get/SetDefaultNamespacePrefix

b.      Get/SetGmlIDRelatePropertyNames

c.       Get/SetGmlNameRelatePropertyName

d.      Get/SetGmlDescriptionRelatePropertyName

If you would like to have them fixed, I can log a ticket for that.



Please let me know your decision. I will update RFC later.



Thanks & regards,

Christine



-----Original Message-----
From: fdo-internals-bounces at lists.osgeo.org [mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Greg Boone
Sent: Friday, April 26, 2013 12:27 AM
To: FDO Internals Mail List
Subject: Re: [fdo-internals] Please review RFC 66



Can you include the detailed design of the managed API in the RFC?



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?



Regards,

Greg





-----Original Message-----

From: fdo-internals-bounces at lists.osgeo.org [mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Christine Bao

Sent: Wednesday, April 24, 2013 9:59 PM

To: FDO Internals Mail List

Subject: Re: [fdo-internals] Please review RFC 66



Thanks Greg for pointing it out. Yes, I will update the managed FDO API also. I updated the RFC to include this.



Thanks & regards,

Christine



-----Original Message-----

From: fdo-internals-bounces at lists.osgeo.org [mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Greg Boone

Sent: Wednesday, April 24, 2013 9:59 PM

To: FDO Internals Mail List

Subject: Re: [fdo-internals] Please review RFC 66



One question...



What about the Managed FDO API?



public ref class XmlFeatureSerializer sealed



                ...\Fdo\Managed\Src\OSGeo\FDO\Xml\mgXmlFeatureSerializer.h





public ref class XmlFeatureFlags : public NAMESPACE_OSGEO_FDO_XML::XmlFlags



                ...\Fdo\Managed\Src\OSGeo\FDO\Xml\mgXmlFeatureFlags.h



Greg





-----Original Message-----

From: fdo-internals-bounces at lists.osgeo.org [mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Jackie Ng

Sent: Tuesday, April 23, 2013 10:27 PM

To: fdo-internals at lists.osgeo.org

Subject: Re: [fdo-internals] Please review RFC 66



No problems from me.



+1 Jackie







--

View this message in context: http://osgeo-org.1560.x6.nabble.com/Please-review-RFC-66-tp5048641p5049256.html

Sent from the FDO Internals mailing list archive at Nabble.com.

_______________________________________________

fdo-internals mailing list

fdo-internals at lists.osgeo.org<mailto:fdo-internals at lists.osgeo.org>

http://lists.osgeo.org/mailman/listinfo/fdo-internals

_______________________________________________

fdo-internals mailing list

fdo-internals at lists.osgeo.org<mailto:fdo-internals at lists.osgeo.org>

http://lists.osgeo.org/mailman/listinfo/fdo-internals

_______________________________________________

fdo-internals mailing list

fdo-internals at lists.osgeo.org<mailto:fdo-internals at lists.osgeo.org>

http://lists.osgeo.org/mailman/listinfo/fdo-internals

_______________________________________________

fdo-internals mailing list

fdo-internals at lists.osgeo.org<mailto:fdo-internals at lists.osgeo.org>

http://lists.osgeo.org/mailman/listinfo/fdo-internals
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/fdo-internals/attachments/20130426/2dc706ea/attachment.html>