* Frédéric Demians (frederic@tamil.fr) wrote:
> I've played with this idea of a cover images centralized cache of URLs.
> I have a mock-up. Anybody interested in testing, commenting?
>
> Client side (Koha), two syspref enable the service. URL are fetched from
> the cache, via JSONP, just Google Books:
>
> http://git.tamil.fr/?p=koha;a=commitdiff;h=e8e223437a5f61c8320cba1b9563a2eb81a6f9f2
>
> Server side, it's a node.js + redis small application:
>
> http://git.tamil.fr/?p=coce;a=commitdiff;h=5e8021a95df07c7a5b14692955ac4c23c7490990
>
> It works now with Amazon and Google Books, but can be extended easily to
> support other providers. It could work with other ILS than Koha. I can
> show how it works on a Koha devel instance.

I was thinking we could do it all client side with js and html5 (and
localstorage or indexdb) You'd define the order in system preferences,
local, google, amazon, ltfl etc. Then the js would try them in that
order and cache the resulting url (or the fact it couldn't find one)
in localstorage or indexdb, which persists even when the browser is
closed.

That way it wouldnt need to be another server/service, since you have
the js already, it shouldn't be too hard to convert it to an html5
client side app.

Thoughts?

Chris

> _______________________________________________
> Koha-devel mailing list
> Koha-devel@lists.koha-community.org
> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : http://www.koha-community.org/
> git : http://git.koha-community.org/
> bugs : http://bugs.koha-community.org/

--
Chris Cormack
Catalyst IT Ltd.
+64 4 803 2238
PO Box 11-053, Manners St, Wellington 6142, New Zealand

_______________________________________________
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/