search

noobdoesre / openjpeg

Automatically exported from code.google.com/p/openjpeg
Other
0 stars 0 forks source link

openjpip vs kdu_show #116

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Right now kdu_show is not capable of talking with openjpip server. I think this 
is very important to make sure openjpip is compatible with kakadu

Original issue reported on code.google.com by mathieu.malaterre on 10 Feb 2012 at 10:23

GoogleCodeExporter commented 9 years ago 
Looks like kdu_show is sending:

"GET /myFCGI?type=jpp-stream&target=16.jp2&tid=0&cnew=http&stream=0&len=2000 
HTTP/1.1"

while openjpip expect something like:

"GET /myFCGI?target=16.jp2&fsiz=170,170&cnew=http&type=jpp-stream HTTP/1.1"

Original comment by mathieu.malaterre on 10 Feb 2012 at 10:30

GoogleCodeExporter commented 9 years ago

Original comment by antonin on 10 Feb 2012 at 1:50

GoogleCodeExporter commented 9 years ago 
Although the 'len' request does not determine unique portions of a codestream, 
the kakadu client seems to expect metadata-bins to obtain the original JP2 file 
structure.

This is enabled in opj_server of svn openjpeg-1.5.

However we have a problem with the next query from the kakadu client.

GET 
/myFCGI?cid=4f4cb3fd643c9869&stream=0&context=jpxl%3C0%3E&metareq=%5B*/ws%5D,%5B
lbl_/sg!%5DD1,%5Blbl_/sg%5D&len=2000&pref=fullwindow

The metareq is unreadable, and pref request is not implemented in opj_server..

Original comment by Kaori.Ha...@gmail.com on 28 Feb 2012 at 11:23

GoogleCodeExporter commented 9 years ago

Original comment by mathieu.malaterre on 25 Feb 2014 at 3:43