Changes between Version 2 and Version 3 of Release/2.2Beta/Notes


Ignore:
Timestamp:
05/03/10 12:53:01 (15 years ago)
Author:
trevorwekel
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • Release/2.2Beta/Notes

    v2 v3  
    2525
    2626== API changes ==#ApiChanges
    27 [wiki:MapGuideRfc66 RFC 66] added client side pinging for the AjaxViewer to keep sessions alive.  API changes include a new HTTP GETSESSIONTIMEOUT and MgSiteConnection.GetSessionTimeout().  An <EnablePingServer> boolean element was added to WebLayout.  Since these are new APIs, there is no impact on existing code.
     27[wiki:MapGuideRfc66 RFC 66] added client side pinging for the !AjaxViewer to keep sessions alive.  API changes include a new HTTP GETSESSIONTIMEOUT and !MgSiteConnection.!GetSessionTimeout().  An <!EnablePingServer> boolean element was added to !WebLayout.  Since these are new APIs, there is no impact on existing code.
    2828
    29 [wiki:MapGuideRfc70 RFC 70] introduced new API for creating and modifying the schema of a feature source.  Delete methods are added to !MgFeatureSchema, !MgClassDefinition and !MgPropertyDefinition.  A new !ApplySchema() method was added to !MgFeatureService.  A Decimal property was added to !MgPropertyType for schema purposes. Since these are new APIs, there is no impact on existing code. 
     29[wiki:MapGuideRfc70 RFC 70] introduces new API for creating and modifying the schema of a feature source.  Delete methods are added to !MgFeatureSchema, !MgClassDefinition and !MgPropertyDefinition.  A new !ApplySchema() method was added to !MgFeatureService.  A Decimal property was added to !MgPropertyType for schema purposes. Since these are new APIs, there is no impact on existing code. 
    3030
    3131
    3232[wiki:MapGuideRfc73 RFC 73] introduces a new !GetResourceContents() API to !MgResourceService.  This new functionality is used internally by !MgMap to reduce web extensions / server crosstalk when creating an !MgMap object from a map definition.  Since this is new API, there is no impact on existing code.
    3333
    34 [wiki:MapGuideRfc74 RFC 74] introduces a boolean "cascade" parameter to MgResourceService.MoveResource().  If cascade is enabled, dependant resources will be updated to point at the new location for the moved resource. Since this is new API, there is no impact on existing code.
     34[wiki:MapGuideRfc74 RFC 74] introduces a boolean "cascade" parameter to !MgResourceService.!MoveResource().  If cascade is enabled, dependant resources will be updated to point at the new location for the moved resource. Since this is new API, there is no impact on existing code.
    3535
    36 [wiki:MapGuideRfc73 RFC 77] allows MgFeatureService.CreateFeatureSource() to create a feature source without defining the feature class and spatial context.  The previous implementation would throw an !MgInvalidArgumentException.  '''This behaviour change may affect existing code.'''
     36[wiki:MapGuideRfc78 RFC 77] allows !MgFeatureService.!CreateFeatureSource() to create a feature source without defining the feature class and spatial context.  The previous implementation would throw an !MgInvalidArgumentException.  '''This behaviour change may affect existing code.'''[[BR]] [[BR]]
     37
     38[wiki:MapGuideRfc78 RFC 78] introduces explicit transaction management for Feature Service.  A new !MgTransaction object is created and !MgFeatureService !ExecuteSqlQuery, !ExecuteSqlNonQuery, and !UpdateFeatures are overloaded to use the new transaction object.  Since this is new API, there is no impact on existing code.
     39
     40[wiki:MapGuideRfc79 RFC 79] adds more detailed exception classes derived from MgFdoException.  The derived classes provide more information than the generic MgFdoException.  Existing code should continue to work with MgFdoException and should be updated to make use of the derived exception classes.
     41
     42[wiki:MapGuideRfc80 RFC 80] adds parameter binding support to !MgFeatureService !ExecuteSqlQuery and !ExecuteSqlNonQuery.  Since this is new API, there is no impact on existing code.
     43
     44[wiki:MapGuideRfc82 RFC 82] extends the !MapGuide readers to support property access by index in addition to property name.  Accessing properties by index instead of property name may be faster for tight loop processing.  Since this is new API, there is no impact on existing code.
     45
    3746 
    3847[wiki:MapGuideRfc89 RFC 89] introduced a number of changes required by the upgrade to PHP 5.3.  '''These changes break existing code.'''