burtonator wrote:
>
> Rapha�l Luta wrote:
> >
> > burtonator wrote:
> > >
> > > This is a quick proposal for building out Jetspeed's WAP support.
> > >
> >
> > I was planning to do this last week-end but got caught in fixing other things
> > in Jetspeed se my other posts...
> >
> <snip>
>
> OK.. .+1
>
> But why does the Profiler need RunData? I would rather not introduce
> this requirement.
>
Well, a Profiler needs to access to the following information to do its job :
- its configuration ( handled by the factory and init calls )
- the request object ( for accessing request parameters, cookies and http headers
such as referer, remote IP, accept-language, etc... )
- the current User information ( for getting user name, preferences, etc... )
Depending, on the complexity of the Profiler involved it may use all or only some
of these informations. Using RunData seemed the most simple way to access all
these things, but any equivalent structure or list of parameters may do.
--
Rapha�l Luta - [EMAIL PROTECTED]
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
