--On Thursday, October 24, 2002 10:55:45 PM +1000 Hugh Irvine
<[EMAIL PROTECTED]> wrote:
Hello Jerome -
I think the correct answer would be to have different processing for
"Timestamp" and "Event-Timestamp", not to override what is currently done
by Radiator with "Timestamp", given that they are different ideas of what
"time" is.
In any case, if "Event-Timestamp" is present in a request, then it will
not interfere with Radiator's own "Timestamp". And it is available as the
special character %{Event-Timestamp}, exactly like %{Timestamp} is, so
you needn't write a hook anyway (as mentioned in my previous mail).
OK, I agree with that.
--
Jerome Fleury
===
Archive at http://www.open.com.au/archives/radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
