[Koha-patches] [PATCH] LibraryThing Cover Images

[Chris Cormack]

* Kyle Hall (kyle.m.hall at gmail.com) wrote:
> On Wed, Sep 16, 2009 at 9:48 AM, Galen Charlton <gmcharlt at gmail.com> wrote:
> > A few ideas come to mind.
> >
> > [1] Continue to use a directory on disk.  However, rather than
> > sticking it in the template directory, we should define a new
> > static_web_cache directory (or two, one for OPAC and one for intranet)
> > whose default location is outside the standard template tree and whose
> > value is set in koha-conf.xml.  That way, we don't reduce the risk of
> > a Koha sysadmin accidentally making the whole of koha-tmpl read/write
> > by the Apache user.
> 
> That sounds like a good idea. I would suggest we have either 1 or 3 of
> these directories. Either 1 shared by both the OPAC and Intranet, or
> one for each plus a shared directory. That way, each image will not
> need to be downloaded twice ( once each for the OPAC and Intranet ).
> Something like:
> /var
>   /koha
>     /intranet
>     /opac
>     /shared
>       /LibraryThing
>         /small
>         /medium
>         /large
> 
> Makes sense to me. What would be the best way to then make it web
> accessible? I imagine some entry in koha's apache conf, but I'm not
> sure what would be the best way to go about doing so.
> 
> > [2] Use memcached.  This would require adding a small web service to
> > fetch and serve images from memcached.
> 
> I'm not familiar with memcached, so I pulled up the wikipedia page on
> it. It looks like is used for caching database queries. Would it work
> for filesystem based storage?
> 
memcached will cache anything you throw at, including serialised perl
objects.

At work we cache entire html pages with it, fragments of html,
serialised objects and the results of db queries.

If you want hop on irc sometime and we can have a chat about it.

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