Less a PR than a friendly hello and thanks and FYI

[thisisaaronland]

Hi,

For a whole bunch of reasons I have been investigating the IIIF Image API lately. As an exercise to better understand the various moving parts I forked your iiif package and started refactoring it so that the processing logic exists inside discrete Go packages rather than the server itself.

There was also a lot of work to define caching strategies for both derivatives and source images (because loading the same giant file to generate tiny slippy-map tiles is sad-making...)

I just merged all of that work in to my copy of master and things seem to work, which is nice because the next step is to write tools for generating derivatives out-of-band.

https://github.com/thisisaaronland/go-iiif

At this point our respective code is wildly out of sync that I am happy just creating a brand new repo (with proper credit of course :-) and we can continue to watch each other over the GitHubs. If you're interested in folding any of this work in to your code then I am happy to talk.

It is worth mentioning that I am planning to extend – and I don't have a good idea of what that actually means – the spec to do some things that we needed for images when I worked at the Cooper Hewitt [1,2] so maybe it's easier just to keep things in separate repos...

Anyway, thanks for all the work that you did! It was very helpful.

[1] http://labs.cooperhewitt.org/2013/b-is-for-beta/
[2] https://github.com/cooperhewitt/py-cooperhewitt-roboteyes

[greut]

Thanks mate.

I've be following your changes with both interest and curiosity. This project was a way to get to learn Go as a language, so it's very good to have another project to look at and take inspiration from.

I've got no direct use of this project as it was only a way to see how it would compete with a Flask-based alternative (PIL).

I'm glad that it was useful to another being. I'll keep an eye on your go-iiif.

This PR can be closed as it feels to radical :-)

Cheers and best of luck!