[mapguide-internals] Refactoring Web .NET API into Common DLLs
is ready for review.
jumpinjackie at gmail.com
Thu Jun 25 21:36:20 EDT 2009
I guess the problem may be that there is a perception that the MapGuide Web
API can only be used for web applications (maybe something to do with having
"Web" in its name? :-))
There are a whole class of ASP.net libraries which share this problem. They
are all .net assemblies, but serve no real purpose when used outside the
context of ASP.net.
So while the MapGuide API may have use outside of web applications. It's not
readily made apparent for the rest of us what these uses could be.
If this splitting into smaller dlls means that I can avoid web-specific
trappings like having to call MgInitializeWebTier() with a webconfig.ini to
start the whole thing, then I would be supportive of such a move.
Leaf Li wrote:
> Thanks for you useful comments. I totally understand your concerns.
> 1. Yes. We didn't see people clamour to re-use the MapGuide APIs outside
> of MapGuide web apps. It is just because we didn't refactor Web API into
> some common dll and users can't do it outside of MapGuide. Through this
> RFC, people will be aware that they can use MapGuide API outside of
> MapGuide. Personally, I believe this RFC is just the first step.
> 2. I think some of open source projects can be beneficial from it such as
> FDO Toolbox. By the refactored API, FDO Toolbox can add more functionality
> easily such as geometry coordinate system transformation.
> 3. Actually there are already some projects and products which is trying
> to reuse MapGuide Web .NET API such as Map 3D. I think they can be
> beneficial from it.
> Leaf Li
> mapguide-internals mailing list
> mapguide-internals at lists.osgeo.org
View this message in context: http://n2.nabble.com/RE%3A-Refactoring-Web-.NET-API-into-Common-DLLs-is-ready-for-review.-tp3154316p3158875.html
Sent from the MapGuide Internals mailing list archive at Nabble.com.
More information about the mapguide-internals