RE: cvs commit: jakarta-jetspeed/webapp/WEB-INF/conf JetspeedReso urces.properties

[Glenn Golden <gg...@umich.edu>]

David -

What's wrong with the caching in a distributed env. With the db psml
manager?

If machine A creates a psml, it goes right to the database, and if a user
comes to machine B with a profile that would pick that, it would find it -
unless it's been cached as missing on B... So you could run the refresher
more often... And B would see the page a little later than it's been
created...

Is this the case you are running into?  Are there others?

Thanks.

- Glenn

> -----Original Message-----
> From: taylor@apache.org [mailto:taylor@apache.org] 
> Sent: Wednesday, September 18, 2002 9:24 PM
> To: jakarta-jetspeed-cvs@apache.org
> Subject: cvs commit: jakarta-jetspeed/webapp/WEB-INF/conf 
> JetspeedResources.properties
> 
> 
> taylor      2002/09/18 18:24:13
> 
>   Modified:    src/java/org/apache/jetspeed/modules/actions/portlets
>                         PsmlBrowseAction.java
>                src/java/org/apache/jetspeed/services/psmlmanager/db
>                         DatabasePsmlManagerService.java
>                webapp/WEB-INF/conf JetspeedResources.properties
>   Log:
>   Added PsmlManager.caching-on property to Jrp. It is used by 
> DatabasePsmlManagerService to enable caching.
>   Removed code to read in data for psml browser from the 
> session, as this action is not tied into the 
> creation/deletion of roles/users etc. Hence the psml entries 
> are invalid in the earlier stated circumstances. Now this 
> action executes the query each time buildNormalContext is called.
>   

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>