Context Navigation

Changes between Version 7 and Version 8 of MapGuideRfc158

v7	v8
40	40
41	41	This is work that client applications do not, and should not have to do.
	42
	43	Another aspect of the mapagent where client applications are doing lots of unnecessary work is the responses for the {{{GETCLASSDEFINITION}}} and {{{DESCRIBESCHEMA}}} requests. The XML response for these requests are raw XML schema definitions returned by the underlying FDO APIs. The converted JSON form of this response is even more horrible to work with. MapGuide Maestro for example, has to employ manual XML parsing of these responses in order to make sense of the schemas/classes of a Feature Source, whereas with other mapagent operations it has the luxury of working with strongly-typed classes auto-generated from various XML schemas for the various responses.
42	44
43	45	== Proposed Solution ==