Changes between Version 2 and Version 3 of rfc36_open_by_drivername
- Timestamp:
- Oct 3, 2011, 12:23:05 PM (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
rfc36_open_by_drivername
v2 v3 49 49 == Issues == 50 50 51 But it is important to note that some drivers already accept a "driver-name:" entry and knows how to deal with it directly. In that case if the driver name entered is exactly the name of a driver then it will take advantage of the proposed mechanism avoiding the probing mechanism. Therefor entries like "GTIFF_RAW:xxx", "GEOR:xxx", "JPEG_SUBFILE:xxx" will fail to be loaded direct by any driver, since they are not real driver snames. The control will be passed to the driver probing loop that will eventually open the file.51 But it is important to note that some drivers already accept a "driver-name:" entry and knows how to deal with it directly. In that case if the driver name entered is exactly the name of a driver then it will take advantage of the proposed mechanism avoiding the probing mechanism. Therefor entries like "GTIFF_RAW:xxx", "GEOR:xxx", "JPEG_SUBFILE:xxx" will fail to be loaded direct by any driver, since they are not real driver names. The control will be passed to the driver probing loop that will eventually open the file. 52 52