Changes between Version 33 and Version 34 of rfc24_progressive_data_support


Ignore:
Timestamp:
Aug 28, 2008, 10:35:18 AM (16 years ago)
Author:
normanb
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • rfc24_progressive_data_support

    v33 v34  
    2525The implementation is a definition of an interface for streaming support data support within GDAL. Concrete implementations of this interface will follow.  Currently the most convenient JPIP streaming developer library is [http://www.kakadusoftware.com Kakadu] however since GDAL is also a developer library, only stubs can be distributed to conform to Kakadu licensing ([http://trac.osgeo.org/gdal/wiki/JP2KAK JP2KAK]).  Vendors are also interested in using GDAL for streaming support and a standard interface will allow these plugins to be incorporated. e.g. [http://www.gdal.org/frmt_jp2ecw.html ECW], [http://www.gdal.org/frmt_mrsid.html MrSID].
    2626
    27 To support reading streaming data from a progressive server it will be necessary to communicate between different threads.  In general it's safer not to do this by shared memory, but by explicit message passing using asynchronous queues. e.g. [http://library.gnome.org/devel/glib/2.12/glib-Asynchronous-Queues.html Glib Asynchronous Queues]
     27To support reading streaming data from a progressive server it will be necessary to communicate between different threads.  In general it's safer not to do this by shared memory, but by explicit message passing using asynchronous queues. e.g. [http://library.gnome.org/devel/glib/2.12/glib-Asynchronous-Queues.html Glib Asynchronous Queues], [http://en.wikipedia.org/wiki/Message_queue Wikipedia Message Queues]
    2828
    2929