Changes between Initial Version and Version 1 of MapGuideRfc28

Timestamp:

Aug 20, 2007, 9:00:30 AM (17 years ago)

Author:

chrisclaydon

Comment:

--

MapGuideRfc28

@@ +1 @@
+= !MapGuide RFC 28 - Web Tier APIs for Fusion support =
+
+This page contains an change request (RFC) for the !MapGuide Open Source project.  
+More !MapGuide RFCs can be found on the [wiki:MapGuideRfcs RFCs] page.
+
+
+== Status == 
+ 
+||RFC Template Version||(1.0)|| 
+||Submission Date||Aug 20, 2007||
+||Last Modified||Chris Claydon [[Timestamp]]||
+||Author||Chris Claydon||
+||RFC Status||draft||
+||Implementation Status||under development||
+||Proposed Milestone||1.3||
+||Assigned PSC guide(s)||(when determined)||
+||'''Voting History'''||none||
+ 
+== Overview ==
+
+This RFC contains a proposal for new web tier APIs to facilitate the creation of the resources required to build a web application based on the new "Fusion" framework.
+
+== Motivation ==
+
+The new application definition framework (aka Fusion) for !MapGuide Open Source web applications is based upon the following components:
+
+1) A set of HTML/CSS templates defining the application's layout and appearance.
+
+2) A set of "widgets" (e.g. Pan, Zoom, Search etc.) that provide functionality for the application.
+
+3) "Application Definition" resources, stored in the MG repository, that provide configuration information for the referenced widgets, and associate them with the panels in an HTML template.
+
+In order to allow authoring applications to build Application Definitions, it must be possible to enumerate the available templates and widgets, and to retrieve information about them.
+
+== Proposed Solution ==
+
+The new APIs would be implemented entirely in the web tier. No modifications are required to the MGOS Server, since the Fusion framework will be part of the web tier deployment.
+
+The APIs would be implemented as HTTP requests, and would use the following operations:
+
+ENUMERATEAPPLICATIONTEMPLATES
+
+ENUMERATEAPPLICATIONWIDGETS
+
+ENUMERATEAPPLICATIONCONTAINERS
+
+Details of each of the new APIs are as follows:
+
+=== ENUMERATEAPPLICATIONTEMPLATES ===
+
+Request parameters:
+
+||FORMAT||text/xml (default) or application/json||
+||REFRESH||0 (default) or 1 to indicate whether to use cached information or to refresh the list from the source files||
+
+Response:
+
+The response will be in XML or JSON format (depending on the FORMAT parameter) and will return the Name, URL, Description and Preview Image URL for each of the available templates.
+
+=== ENUMERATEAPPLICATIONWIDGETS ===
+
+Request parameters:
+
+||FORMAT||text/xml (default) or application/json||
+||REFRESH||0 (default) or 1 to indicate whether to use cached information or to refresh the list from the source files||
+
+Response:
+
+The response will be in XML or JSON format (depending on the FORMAT parameter) and will return the Name, Description and Preview Image URL for each of the available widgets.
+
+=== ENUMERATEAPPLICATIONCONTAINERS ===
+
+Request parameters:
+
+||FORMAT||text/xml (default) or application/json||
+||REFRESH||0 (default) or 1 to indicate whether to use cached information or to refresh the list from the source files||
+
+Response:
+
+The response will be in XML or JSON format (depending on the FORMAT parameter) and will return the Name, Description and Preview Image URL for each of the available container types. Examples of containers are: Toolbar, Context Menu, Status Bar.
+
+== Implications ==
+
+The implementation is entierly in the web tier. All APIs are new and do not affect existing APIs or functionality.
+
+== Test Plan ==
+
+Testing should be carried out by exercising the HTTP APIs in unit tests and via authoring applications.
+
+== Funding/Resources ==
+
+Funding and resources to be supplied by Autodesk.