| | 1 | = !MapGuide RFC 70 - Apply Schema = |
| | 2 | |
| | 3 | This page contains an change request (RFC) for the !MapGuide Open Source project. |
| | 4 | More !MapGuide RFCs can be found on the [wiki:MapGuideRfcs RFCs] page. |
| | 5 | |
| | 6 | |
| | 7 | == Status == |
| | 8 | |
| | 9 | ||RFC Template Version||(1.0)|| |
| | 10 | ||Submission Date||June 23, 2009|| |
| | 11 | ||Last Modified||Leaf Li [[Timestamp]]|| |
| | 12 | ||Author||Leaf Li|| |
| | 13 | ||RFC Status||draft|| |
| | 14 | ||Implementation Status||under development|| |
| | 15 | ||Proposed Milestone||2.2|| |
| | 16 | ||Assigned PSC guide(s)||Tom Fukushima|| |
| | 17 | ||'''Voting History'''||(vote date)|| |
| | 18 | ||+1|||| |
| | 19 | ||+0|||| |
| | 20 | ||-0|||| |
| | 21 | ||-1|| |
| | 22 | ||no vote|| || |
| | 23 | |
| | 24 | == Overview == |
| | 25 | |
| | 26 | This proposal is to refactor MapGuide Web .NET API to some common dlls. |
| | 27 | |
| | 28 | == Motivation == |
| | 29 | |
| | 30 | Currently all MapGuide Web .NET API is in one single dll !MapGuieDotNetApi.dll, which includes Foundation, Geometry, !PlatformBase, !MapGuideCommon, !WebApp and !HttpHandler components. It isn’t good for users to reuse functionality provided by MapGuide Web .NET API. For example, users have to include a reference to all components even if they just want to use Geometry related API. |
| | 31 | |
| | 32 | == Proposed Solution == |
| | 33 | |
| | 34 | MapGuide Web .NET API will be divided into five separated dlls. SWIG is used to create MapGuide .NET API as before. |
| | 35 | * OSGeo.!MapGuide.Foundation.dll: contains API in Foundation component. |
| | 36 | * OSGeo.!MapGuide.Geometry.dll: contains API in Geometry compoent. |
| | 37 | * OSGeo.!MapGuide.!PlatformBase.dll: contains API in !PlatformBase component. |
| | 38 | * OSGeo.!MapGuide.!MapGuideCommon.dll: contains API in !MapGuideCommon compoent. |
| | 39 | * OSGeo.!MapGuide.Web.dll: contains API in !WebApp and !HttpHandler components. |
| | 40 | |
| | 41 | == Implications == |
| | 42 | |
| | 43 | Currently, there is no enough resources and funding to refator PHP and Java API. They may be implemented if resources and funding can be obtained in the future. |
| | 44 | |
| | 45 | == Test Plan == |
| | 46 | |
| | 47 | Run the existing unit tests. No need to add new unit tests. |
| | 48 | |
| | 49 | == Funding/Resources == |
| | 50 | |
| | 51 | Supplied by Autodesk. |
