Changes between Version 38 and Version 39 of rfc24_progressive_data_support

Timestamp:

Aug 28, 2008, 12:45:24 PM (16 years ago)

Author:

normanb

Comment:

--

rfc24_progressive_data_support

@@ -33 +33 @@
 [[Image(class.png)]]
 
-Implementing !GDALAsyncDataset allows the user application to decide when and how often the updates occur, and reduces the potential negative impacts of threading by providing a clear synchonization point, !NextAsyncRasterIOMessage().
+Implementing GDALAsyncDataset allows the user application to decide when and how often the updates occur, and reduces the potential negative impacts of threading by providing a clear synchonization point, NextAsyncRasterIOMessage().
 
-!GDALAsyncRasterIOMessage contains a buffer that is described the getParameters() function which returns a struct with the parameters passed into ProgressiveRasterIO.  Note that no lock() / unlock() on the buffer is required as each buffer represents a call to the server and is a separate instance. 
+GDALAsyncRasterIOMessage contains a buffer that is described the getParameters() function which returns a struct with the parameters passed into ProgressiveRasterIO.  Note that no lock() / unlock() on the buffer is required as each buffer represents a call to the server and is a separate instance. 
 
-Each !GDALAsyncRasterIOMessage will be small, it only contains the data for the currently requested window at a particular resolution level. These requests are usually proportional, i.e small window implies high resolution, large window implies low resolution. 
+Each GDALAsyncRasterIOMessage will be small, it only contains the data for the currently requested window at a particular resolution level. These requests are usually proportional, i.e small window implies high resolution, large window implies low resolution.