You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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
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:
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
A callback can be used to create a codestream object from the results of the parser
The text was updated successfully, but these errors were encountered:
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:
Some initial thoughts on how to proceed:
The text was updated successfully, but these errors were encountered: