| | 1 | [[PageOutline]] |
| | 2 | |
| | 3 | This page is part of the [wiki:Future MapGuide Future] section, where ideas are proposed and refined before being turned into RFCs (or discarded). Visit the [wiki:Future] page to view more! |
| | 4 | |
| | 5 | = Overview = |
| | 6 | |
| | 7 | Currently, !MapGuide uses a modular services approach for core functionality, such as data access, rendering, etc. |
| | 8 | |
| | 9 | Ideally, this approach could be made "pluggable" so that independant developers could easily create modules (such as !GeoCoding and Routing perhaps) that could extend the core !MapGuide functionality. Existing unused modules could also be removed at installation time to reduce the attack surface. |
| | 10 | |
| | 11 | This would require a module registry system, similar to the provider registry used with FDO. and perhaps some way of indicating dependancies between modules. |
| | 12 | |
| | 13 | It is not clear what the technical changes required for this would be, but with a well-documented module development guide / API (bite-sized), this could encourage further developer involvement in !MapGuide. |
