|
From the mailing list:
Hi,
the Dispatcher.REQUEST thread local has proven to be quite useful in various
integration/custom development scenarios where we needed to get some extra
information about the incoming request (like, for example, accessing to vendor parameters
in a custom store implementation).
So far, so good, but I'm finding myself repeating over and over the same workarounds
to access the parsed request object, that is, create a dispatcher callback for the sole
reason of snatching the parsed request object in the operationDispatched callback,
put it in a thread local, to access is later.
I was wondering, would you mind if we put the Operation, or maybe just the
Object[] parameters of it, as a new field in Request?
|
Major
