Changes between Version 71 and Version 72 of rfc24_progressive_data_support

Timestamp:

Apr 8, 2009, 5:04:41 PM (15 years ago)

Author:

normanb

Comment:

--

rfc24_progressive_data_support

@@ -83 +83 @@
 C API to `JPIPKAKDataset->GetMetadata`
 
-5. GetMetadata
+5. !GetMetadata
 
 returns metadata for the "JPIP" domain, keys are "JPIP_NQUALITYLAYERS", "JPIP_NRESOLUTIONLEVELS", "JPIP_NCOMPS" and "JPIP_SPRECISION"
@@ -115 +115 @@
 13. GDALLockBuffer
 
-C API to LockBuffer
+C API to !LockBuffer
 
-14. LockBuffer
+14. !LockBuffer
 
 Not implemented in `JPIPKAKAsyncRasterIO`, a lock is acquired in `JPIPKAKAsyncRasterIO->GetNextUpdatedRegion`
@@ -123 +123 @@
 15. GDALGetNextUpdatedRegion
 
-C API to GetNextUpdatedRegion
+C API to !GetNextUpdatedRegion
 
-16. GetNextUpdatedRegion
+16. !GetNextUpdatedRegion
 
 The function decompresses the available data to generate an image (according to the dataset buffer type set in `JPIPKAKDataset->BeginAsyncRasterIO`) The window width, height (at the requested discard level) decompressed is returned in the region pointer and can be rendered by the client. The status of the rendering operation is one of `GARIO_PENDING`, `GARIO_UPDATE`, `GARIO_ERROR`, `GARIO_COMPLETE` from the `GDALAsyncStatusType` structure. `GARIO_UPDATE`, `GARIO_PENDING` require more reads of `GetNextUpdatedRegion` to get the full image data, this is the progressive rendering of JPIP. `GARIO_COMPLETE` indicates the window is complete.
@@ -135 +135 @@
 17. GDALUnlockBuffer
 
-C Api to UnlockBuffer
+C API to !UnlockBuffer
 
-18. UnlockBuffer
+18. !UnlockBuffer
 
 Not implemented in `JPIPKAKAsyncRasterIO`, a lock is acquired in `JPIPKAKAsyncRasterIO->GetNextUpdatedRegion`
@@ -147 +147 @@
 20. GDALLockBuffer
 
-21. LockBuffer
+21. !LockBuffer
 
 22. GDALGetNextUpdatedRegion
 
-23. GetNextUpdatedRegion
+23. !GetNextUpdatedRegion
 
-24. GDALUnlockBuffer
+24. !GDALUnlockBuffer
 
 25. UnlockBuffer