pantelisgeorgiadis / htj2k-js Goto Github PK

This will allow it to minimize memory usage

Once paused, any new data pushed to it will be queued. Once unpaused it will resume parsing any queued data

It should be able to cancel parsing. Once cancelled, the parser cannot be resumed. All data it receives after being cancelled is discarded

Currently the parse results (e.g. codestream.segments, codestream.tiles) is tightly coupled to the parsing logic (codestream.decode()) logic. These should be separated for a few reasons:

1. the parsing code can be re-used without having to do decoding. A few examples come to mind - a simple codestream dump utility, code that needs to implement sub resolution fetching, JPIP server
2. The decoding logic can be re-used independently of the HTJ2K code stream itself. A few examples come to mind - JPIP client, resumable decoder (e.g. progressive decoding client side)

Some initial thoughts on how to proceed:

1. Pass a callback class to the parser which gets called as the parser works. This is like a SAX based parser. The callback should be able to cancel or pause parsing
2. A callback can be used to create a codestream object from the results of the parser