Rapha�l Luta wrote:
>
> burtonator wrote:
> >
> > 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.
> >
>
> HttpServletRequest or an equivalent wrapper
ug... no HttpServletRequest :(... wrapper...
> > 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.
> >
>
> There's currently no way to stroe request parameters in the Profiler because,
> the default implementation is a Singleton shared for all requests...
So why are we giving it RunData.
> > The problem is that if we give people rundata.. (IE a rope) they might
> > do bad things (like hang themselves :)
> >
>
> Yes, maybe we should just build a RunData-lite, without the rope :)
yup :)
> It's just simpler to use
> getResourceURL( RunData )
> that
> getResourceURL( ParameterParser, User, HttpServletRequest )
... just not the HttpServletRequest.
--
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]
