[mapguide-internals] MapGuide RFC 53 Review

[Steve Dang]

Comma or tab was one of my choices I had in mind but unfortunately they are not reserved characters for class names because FDO separates schema and class name by ":", and class and property name by ".".

Thanks,
Steve.

-----Original Message-----
From: mapguide-internals-bounces at lists.osgeo.org [mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Zac Spitzer
Sent: Monday, August 18, 2008 12:59 PM
To: MapGuide Internals Mail List
Subject: Re: [mapguide-internals] MapGuide RFC 53 Review

Is there a reason for using a period and not a comma to seperate class names?

CLASSNAMES=Class1.Class2.Class3
  vs
CLASSNAMES=Class1,Class2,Class3

z


On Tue, Aug 19, 2008 at 4:39 AM, Jason Birch <Jason.Birch at nanaimo.ca> wrote:
> Can't comment on the implementation, but this is an important addition
> to MapGuide when interacting with DBMS-based feature sources.
>
> I'm assuming that you will be testing the command capabilities to
> determine which providers to call the old mechanism for?
>
> Jason
>
> -----Original Message-----
> From: Steve Dang
> Subject: [mapguide-internals] MapGuide RFC 53 Review
>
> Please review MapGuide RFC 53 (DescribeSchema, DescribeSchemaAsXml,
> GetSchemas and GetClasses API Enhancements),
> http://trac.osgeo.org/mapguide/wiki/MapGuideRfc53, and send any comment
> to this mail list.
> _______________________________________________
> mapguide-internals mailing list
> mapguide-internals at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
>



--
Zac Spitzer -
http://zacster.blogspot.com (My Blog)
+61 405 847 168
_______________________________________________
mapguide-internals mailing list
mapguide-internals at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-internals