[
http://jira.amdatu.org/jira/browse/AMDATU-233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=10779#comment-10779
]
Angelo van der Sijpt commented on AMDATU-233:
---------------------------------------------
I don't really understand the problem or the solution. Is the problem that my
browser caches the gadget, including its security token? If so, why would the
fix in 545 fix that?
It seems reasonable that, when the same uri comes along, an http server returns
a cached response. For personalized data that 'lives' on the same uri, this
should be handled in a special way. How does opensocial propose that you do
this? Is the no-cache solution the proposed one, or do they propose some sort
of uri-discrimination mechanism by e.g. adding the security token in the
request?
> Caching issue in dashboard
> --------------------------
>
> Key: AMDATU-233
> URL: http://jira.amdatu.org/jira/browse/AMDATU-233
> Project: Amdatu
> Issue Type: Bug
> Components: Amdatu OpenSocial
> Affects Versions: 0.1.0
> Reporter: Ivo Ladage - van Doorn
> Assignee: Angelo van der Sijpt
> Fix For: 0.1.0
>
>
> There are some caching issues in the dashboard:
> - When both users georged and janed have the course gadget in their dashboard
> and I log in as georged, I see courses of georged. When I log out, log in as
> janed and refresh the dashboard I still see the courses of georged
> - If I log in as georged, open add gadget popup, close it, log out, log in as
> janed, open add gadget pop up and add a gadget, that gadget contains the
> security token of georged instead of janed (wrong courses in course gadget
> are displayed for example)
> -
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
