-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeff Shell wrote:
> 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 se
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 fr
Martijn Faassen 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 knowin
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
outp
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.
On 12/19/05, Ji
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I have got the error message too just now. But with branch 3.2, Revision
40863. And running on Windows in an instance which was created with
mkzopeinstance.
Egon
Stephan Richter schrieb am 14.12.2005 23:39:
> Hi Peter,
>
> sorry for the long d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim Fulton wrote:
> When we refactored the Zope 3 pubisher to work more closely with WSGI,
> we decided to remove the response.write method. We should have written
> a proposal for this, but we failed to do so. Over the last few weeks
> there has be
Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim Fulton wrote:
When we refactored the Zope 3 pubisher to work more closely with WSGI,
we decided to remove the response.write method. We should have written
a proposal for this, but we failed to do so. Over the last few wee
When we refactored the Zope 3 pubisher to work more closely with WSGI,
we decided to remove the response.write method. We should have written
a proposal for this, but we failed to do so. Over the last few weeks
there has been much discussion of this in which I asserted many times
that I didn't
