Mailing-List: contact jetspeed-dev-help@portals.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jetspeed Developers List" <jetspeed-dev@portals.apache.org>
Message-ID: <3662713.1181264008242.JavaMail.jira@brutus>
Date: Thu, 7 Jun 2007 17:53:28 -0700 (PDT)
From: "David Sean Taylor (JIRA)" <jetspeed-dev@portals.apache.org>
To: jetspeed-dev@portals.apache.org
Subject: [jira] Resolved: (JS2-663) Problem with cacheing key generation
In-Reply-To: <3583821.1173784149264.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/JS2-663?page=3Dcom.atlassian.j=
ira.plugin.system.issuetabpanels:all-tabpanel ]

David Sean Taylor resolved JS2-663.
-----------------------------------

    Resolution: Fixed

This patch committed today should address your issues, and additionally ano=
ther bug with switching between /desktop and /portal mode serving up bad li=
nks via the cache. The default setting is now using a key of (sessionid + p=
ipeline + windowid), so the guest problem you described should be fixed


> Problem with cacheing key generation
> ------------------------------------
>
>                 Key: JS2-663
>                 URL: https://issues.apache.org/jira/browse/JS2-663
>             Project: Jetspeed 2
>          Issue Type: Bug
>          Components: Aggregation
>    Affects Versions: 2.1, 2.2
>            Reporter: Joachim M=C3=BCller
>            Assignee: David Sean Taylor
>
> The key for the portlet content cache consists off the principals name an=
d the OID of the portlet fragment.=20
> This has some problems:
> 1.)  For the anonymous user (principal name =3D "guest"), all anonymous u=
sers will be served the portlet content from the cache, regardless the sess=
ion preferences they changed (i.e. language settings).
> 2.) We do use the ability of jetspeed to inject servlet-request parameter=
s into portlet requests  (not according to JSR-168, but pretty usefull). Ca=
ching does not take the URL request parameters into account. Changing the r=
equest parameters will not be reflected by the porlets content if it's chac=
hed.
> I would propose to make the cache key generation configurable (via spring=
). The default jetspeed cache key generation can use the principals name/fr=
agments OID. As an alternative the cache key should be possible to build up=
on session ID, query parameter and fragments OID. The interface should prov=
ide the cache key generator implementations with the appropriate parameters=
 (i.e. request) to obtain the informations it needs.

--=20
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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