[mapguide-dev] Unmanaged Data APIs RFC

[Andy Morsell]

I really think this is badly needed piece of functionality so I am fully
supportive of it.  Storing the paths in serverconfig.ini sounds like a
reasonable approach.  I'm wondering if aliases of some sort will be used to
discern directories of files?  
 
What I'm afraid of happening is much like how MapGuide 5 and below worked
with SDF files (and how 6.5 still works with raster): when you are choosing
a feature source to author from a GUI, all of the paths are enumerated and
the results listed together.  This can get very cumbersome for people who
work on many simultaneous projects on the same server (like me).  I would
personally like to see this taken one step further where you have separate
lines in an Unmanaged Data Paths section, with one alias per directory.
Then, when choosing the feature source in Studio, Web Studio or whatever, it
would initially display the individual aliases, the user would choose the
pertinent alias, and then that single directory would be enumerated for the
feature sources.  I realize this is an extra piece of functionality, but I
would rather see it done this way from the start.
 
Also, will the user be able to configure these folders through any GUI?  How
about a new section in Server Admin that allows the users to set these
aliases up and browse to the folder?  The resultant information could then
be written into serverconfig.ini.
 
Thanks.  
 

Andy Morsell, P.E. 
Spatial Integrators, Inc. 
http://www.SpatialGIS.com 

  _____  

From: Tony Fang [mailto:tony.fang at autodesk.com] 
Sent: Thursday, November 02, 2006 4:35 PM
To: dev at mapguide.osgeo.org
Subject: [mapguide-dev] Unmanaged Data APIs RFC



I have just posted a draft of the RFC for "Unmanaged Data APIs" in MGOS to
the following location:

 

http://wiki.osgeo.org/index.php/MapGuide_RFC_2_-_Unmanaged_Data_APIs

 

Please take a look, and post any feedback to this group.

 

Thanks,

Tony Fang

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/mapguide-internals/attachments/20061102/e84d728c/attachment.html