> Bernhard Huber wrote:
>
> Hi,
> What do hope to get by this unique request-id later?
> Aren't user-id more interesting, so you can figure out
> who has done what, http-request level may be too fine-grained.
The user-id (or ip-address) is of course very interesting
(if the user is not behind a firewall). It can already be
included in the log, as the Request/Response objects are
available in the log target.
But a unique request-id can be used to filter the log
to get all log entries which belong to one single request.
The id itself has no meaning.
Carsten
>
> ----- Originalnachricht -----
> Von: "Carsten Ziegeler" <[EMAIL PROTECTED]>
> Datum: Dienstag, August 14, 2001 5:33 pm
> Betreff: [C2]: Unique request id
>
> > Hi,
> >
> > here another thought about logging:
> >
> > What about adding a unique identifier for the current request?
> > This would allow us to identify which log entries belong to
> > one single request. (Currently thread id and request uri
> > could be used, but are of course not very usefull as at a
> > later time the same thread id with the same request uri
> > could be invoked).
> >
> > Is there any value we could use for this provided by the
> > servlet api? If not what about adding a simple static
> > counter for this.
> >
> > Thoughts?
> >
> > Carsten
> >
> > -------------------------------------------------------------------
> > --
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, email: [EMAIL PROTECTED]
> >
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
