Changes between Version 12 and Version 13 of FdoEnhancedVersionSupport


Ignore:
Timestamp:
Oct 19, 2007, 9:40:51 AM (17 years ago)
Author:
gregboone
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • FdoEnhancedVersionSupport

    v12 v13  
    66This document contains a design for some software and file version handling strategies for FDO. The versions dealt by this document are:
    77
    8 • Version of FDO software[[br]]
    9 • FDO provider versions[[br]]
    10 • XML configuration file versions[[br]]
     8        • Version of FDO software[[br]]
     9        • FDO provider versions[[br]]
     10        • XML configuration file versions[[br]]
    1111
    1212In FDO 3.0, a number of issues arose regarding the handling of these versions. There were a number of concerns as to how these versions should be handled going forward. The main purpose of this design is to resolve these issues so that customers and client applications can easily upgrade to new FDO software releases as they become available.
    … …  
    3838the following table shows which provider is returned by the FAM, depending on the requested name.
    3939
    40 Client requested -------- FAM returns
    41 
    42 OSGeo.SDF ------------- OSGeo.SDF.5.0[[br]]
    43 OSGeo.SDF.3 ----------- OSGeo.SDF.3.2[[br]]
    44 OSGeo.SDF.4 ----------- OSGeo.SDF.4.0[[br]]
    45 OSGeo.SDF.3.1 --------- OSGeo.SDF.3.1[[br]]
     40||'''Client Requested'''||'''FAM Returns'''||
     41||OSGeo.SDF||OSGeo.SDF.5.0||
     42||OSGeo.SDF.3||OSGeo.SDF.3.2||
     43||OSGeo.SDF.4||OSGeo.SDF.4.0||
     44||OSGeo.SDF.3.1||OSGeo.SDF.3.1||
    4645
    4746The client decides how precise the search is by how many version parts are included in the requested provider name.
    … …  
    107106A provider is considered to be binary-compatible with the current FDO if the specified parts of the provider's !FeatureDataObjectsVersion match those of the current version of FDO. For example, if the !FeatureDataObjectsVersion has 2 parts, then these must match the 1st 2 parts of the current FDO's version. The following table provides some concrete examples:
    108107
    109 ''Provider !FeatureDataObjectsVersion''
    110 
    111 3
    112 
    113 ''Compatible versions of FDO core''
    114 
    115 3.0.0.0[[br]]
    116 3.1.0.0[[br]]
    117 3.2.0.1[[br]]
    118 
    119 ''Incompatible FDO versions''
    120 
    121 2.0.0.0[[br]]
    122 4.0.0.0[[br]]
    123 4.1.0.0[[br]]
    124 
    125 ''Provider !FeatureDataObjectsVersion''
    126 
    127 3.0
    128 
    129 ''Compatible versions of FDO core''
    130 
    131 3.0.0.0[[br]]
    132 3.0.1.0[[br]]
    133 
    134 ''Incompatible FDO versions''
    135 
    136 2.0.0.0[[br]]
    137 3.1.0.0[[br]]
    138 3.2.0.0[[br]]
    139 
    140 ''Provider !FeatureDataObjectsVersion''
    141 
    142 3.2
    143 
    144 ''Compatible versions of FDO core''
    145 
    146 3.2.0.0[[br]]
    147 3.2.1.0[[br]]
    148 
    149 ''Incompatible FDO versions''
    150 
    151 3.1.0.0[[br]]
    152 3.1.1.0[[br]]
    153 3.3.0.0[[br]]
    154 
    155 ''Provider !FeatureDataObjectsVersion''
    156 
    157 3.1.0.1
    158 
    159 ''Compatible versions of FDO core''
    160 
    161 3.1.0.1
    162 
    163 ''Incompatible FDO versions''
    164 
    165 3.1.0.0[[br]]
    166 3.1.0.2[[br]]
    167 3.1.2[[br]]
     108||'''Provider !FeatureDataObjectsVersion'''||'''Compatible Versions of FDO'''||'''Incompatible FDO Versions'''||
     109||3||3.0.0.0||2.0.0.0
     110||||3.1.0.0||4.0.0.0||
     111||||3.2.0.1||4.1.0.0||
     112||||||||
     113||3.0||3.0.0.0||2.0.0.0
     114||||3.0.1.0||3.1.0.0||
     115||||||3.2.0.0||
     116||||||||
     117||3.2||3.2.0.0||3.1.0.0
     118||||3.2.1.0||3.1.1.0||
     119||||||3.3.0.0||
     120||||||||
     121||3.1.0.1||3.1.0.1||3.1.0.0
     122||||||3.1.0.2||
     123||||||3.1.2||
    168124
    169125The 4th example is for illustration and would not likely happen in the real world. It is unlikely that versions as similar as 3.1.0.1 and 3.1.0.2 would be incompatible.