Rapha�l Luta wrote:
<snip>
> 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.
OK. Check out ParameterParser and User. Both of these objects should
give you 60% of your functionality.
The rest, referer, remoteIP, accept-language, etc will have to be done
with our own object.
I was doign this with PortletConfig as you can see. Maybe we can use
your peer class Config as a basis for a ProfilerConfig so that we don't
have to include rundata.
The problem is that if we give people rundata.. (IE a rope) they might
do bad things (like hang themselves :)
Kevin
--
Kevin A Burton (e-mail: [EMAIL PROTECTED], UIN: 73488596, ZKey:
burtonator)
http://relativity.yi.org
Message to SUN: "Please Open Source Java!"
To fight and conquer in all your battles is not supreme excellence;
supreme
excellence consists in breaking the enemy's resistance without fighting.
- Sun Tzu, 300 B.C.
--
--------------------------------------------------------------
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]
