On 1 May 2005, at 13:44, Sylvain Wallez wrote:
Antonio Gallardo wrote:
Hi:
This is only related to the time format in the access output.
Currently we
use:
Processed by Apache Cocoon 2.1.8-dev in 3.612 seconds.
Processed by Apache Cocoon 2.1.8-dev in 3 milliseconds.
New format (an ISO8601-like):
P
On Dom, 1 de Mayo de 2005, 10:31, Stefano Mazzocchi dijo:
> Antonio Gallardo wrote:
>> Hi:
>>
>> This is only related to the time format in the access output. Currently
>> we
>> use:
>>
>> Processed by Apache Cocoon 2.1.8-dev in 3.612 seconds.
>> Processed by Apache Cocoon 2.1.8-dev in 3 millisecon
Antonio Gallardo wrote:
Hi:
This is only related to the time format in the access output. Currently we
use:
Processed by Apache Cocoon 2.1.8-dev in 3.612 seconds.
Processed by Apache Cocoon 2.1.8-dev in 3 milliseconds.
New format (an ISO8601-like):
Processed by Apache Cocoon 2.1.8-dev in 0:00:03.61
Il giorno 01/mag/05, alle 14:38, Antonio Gallardo ha scritto:
Hi:
This is only related to the time format in the access output.
Currently we
use:
Processed by Apache Cocoon 2.1.8-dev in 3.612 seconds.
Processed by Apache Cocoon 2.1.8-dev in 3 milliseconds.
New format (an ISO8601-like):
Processed
Antonio Gallardo wrote:
Hi:
This is only related to the time format in the access output. Currently we
use:
Processed by Apache Cocoon 2.1.8-dev in 3.612 seconds.
Processed by Apache Cocoon 2.1.8-dev in 3 milliseconds.
New format (an ISO8601-like):
Processed by Apache Cocoon 2.1.8-dev in 0:00:03.61
Hi:
This is only related to the time format in the access output. Currently we
use:
Processed by Apache Cocoon 2.1.8-dev in 3.612 seconds.
Processed by Apache Cocoon 2.1.8-dev in 3 milliseconds.
New format (an ISO8601-like):
Processed by Apache Cocoon 2.1.8-dev in 0:00:03.612
Processed by Apach