Il giorno 03/feb/06, alle ore 00:32, David Crossley ha scritto:
I got it a few days ago. Perhaps you re-attached the
same patch.
Took a while for me to find the time to do something about this, but
I have a new version of the patch attached to the issue. You might
want to test it.
Il giorno 29/dic/05, alle ore 23:45, Sylvain Wallez ha scritto:
Ears aren't deaf, but on vacation :-)
Going to be deaf in a couple of days due to firecrackers anyway ;)
I don't understand why you need a ThreadLocal. Isn't a class member
good enough?
How would a class member work with
Ugo Cei wrote:
Il giorno 29/dic/05, alle ore 23:45, Sylvain Wallez ha scritto:
I don't understand why you need a ThreadLocal. Isn't a class member
good enough?
How would a class member work with multiple threads?
I see. This is because the HttpSource is referenced by the
Il giorno 30/dic/05, alle ore 16:09, Sylvain Wallez ha scritto:
I don't understand why you need a ThreadLocal. Isn't a class
member good enough?
How would a class member work with multiple threads?
I see. This is because the HttpSource is referenced by the
HttpSourceValidity, right? Now
On 12/30/05, Sylvain Wallez [EMAIL PROTECTED] wrote:
Other issues that I'm going to dive into are redirects and cache
control. I'm afraid that if we want to make Cocoon into a well-behaved
participant in a Web 2.0 world, we have lots of work to do.
Indeed. My impression is that this work
Ugo Cei wrote:
Given the time of year, I'm afraid this message will fall on deaf
ears, but anyway...
Ears aren't deaf, but on vacation :-)
I was recently startled to discover that there's apparently no easy
way to perform a proper conditional GET [1] using Cocoon's sources.
I wonder: didn't
* Ugo Cei:
Given the time of year, I'm afraid this message will fall on
deaf ears, but anyway ...
Some of us are still listening ;-)
I was recently startled to discover that there's apparently no
easy way to perform a proper conditional GET [1] using
Cocoon's sources. I
