Yes, it's hurry.file. What's Tramline?
We're using hurry.file for small images, generally, and it's been
working fine. We've recently written a cache manager that writes the
images out to the file system where Apache can serve them. So when
that's in place (and working), efficient image serving from Zope is
not that big of a concern to us...
But back to the issue at hand - knowing how to better serve those out
to the response would be a big help.
On 12/19/05, Martijn Faassen <[EMAIL PROTECTED]> wrote:
> Jeff Shell wrote:
> > I was using it in some custom views for HurryFile based images. I've
> > removed it since I started testing our code against Zope 3.2. Right
> > now I just return the hurryfile binary data with a return statement
> > (one big chunk), but am looking forward to knowing how to return long
> > output.
> Is HurryFile the same as hurry.file? You know of course hurry.file is
> pretty inefficient if you don't use tramline (which still needs
> integration into hurry, patches welcome :).
Zope3-dev mailing list