portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Sean Taylor" <da...@bluesunrise.com>
Subject RE: Putting .psml/markup info into database
Date Tue, 10 Jul 2001 16:47:33 GMT
Raphael Luta wrote:
> +1 for list(locator) being in Profiler. It's definitely
> Profiler's job to do
> that, although I would amend the interface to
> public Iterator list( RunData data, ProfileLocator locator )
> or
> public Iterator list( User user, ProfileLocator locator )
> or
> add a get/setUser() in ProfileLocator to put in the RunData User object.
> Why ? Imagine I want to write an alternate adaptive Profiler that stores
> persistent information in the User profile... I need to be able to access
> a pointer to the User.
> ... All in all, I think the third option is the best, it replaces
> the string
> user parameter that was there before and gives a lot more power to the
> profiling interface and enables a trivial implementation of a
> DB-backed PSML
> implementation (just store PSML as BLOB using setPerm())
> What do you think ?

Good point, I will update the ProfilerLocator to have a User object instead
of a String.
Do you hold the same argument for Roles?

To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org

View raw message