Ruven

I've just committed this update: https://github.com/ruven/iipsrv/commit/41d44cbd46da39ab8e9617d52d76fc02d3d813de, which handles both errors and warnings from libtiff. I had to do something more generic, so that both Kakadu, OpenJPEG and any future codecs...

I've made an official docker image for the 1.2 release (based on Alpine Linux). It uses the Alpine iipsrv package with Lighttpd as a web front-end to provide a fully...

Yes, this image is nice and small - only about 12MB! I've looked into making multi-arch builds and it's not too difficult. I've updated the images to include all the...

Version 1.2 now officially released: https://github.com/ruven/iipsrv/releases/tag/iipsrv-1.2

> If we think about IIP serve to include the computing power in browser, why couldn't we manipulate tiles in browser platform such as WASM and keep all tiles static...

When we started IIPImage, there were indeed no good open source light-weight http libraries we could use. Also FastCGI is a much faster and leaner protocol than HTTP and is...

>I mean keep alive connections between the frontend-server and the iipsrv. If I've understood correctly, you're using HTTP between your front-end server and your various Nginx/iipsrv backends? In theory, it...

> The connection between the frontend-server (nginx) and the various iipsrv instances is of course in fastcgi, how else could it be? Sorry, I thought you were using HTTP 1.1...

But how would the server know how many layers to decode for a particular image? Don't forget, there's the existing LYR parameter. Doesn't this do what you need? For each...

> We would have to update the metadata to let the server know. So, this would be a fixed value in the JPEG2000 metadata? That's certainly possible, but the problem...