[
https://jira.duraspace.org/browse/DS-871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=19868#action_19868
]
Robin Taylor commented on DS-871:
---------------------------------
Looks like I'm one of those that clearly need to understand it better :)
Apologies for wasting your time Peter.
The best documentation I can find on how caching works is
http://cocoon.apache.org/2.1/userdocs/concepts/caching.html. My understanding
was that "The pipeline process is cached up to the most possible point", so by
making a component in the pipeline non-cacheable that would force Cocoon to
regenerate the XML events from that point onward in the pipeline. I dont really
understand how the caching in earlier aspects affects the caching of the
particular transformer in question. Wish I could find some better
documentation.
> XMLUI caches community / collection page which doesn't show a recently
> submitted item immediately
> -------------------------------------------------------------------------------------------------
>
> Key: DS-871
> URL: https://jira.duraspace.org/browse/DS-871
> Project: DSpace
> Issue Type: Bug
> Components: XMLUI
> Affects Versions: 1.7.0, 1.7.1
> Reporter: Peter Dietz
>
> With discovery disabled in xmlui, a recently submitted item does not show on
> the recently submitted items list for the collection or community page, until
> the page cache expires. This may be by design, but it is a route that a user
> may be expecting to find their recently submitted item.
> Perhaps on submission, the cache for the parent container pages can be
> invalidated so that the next page view of it will get the recently submitted
> item in the list.
> To reproduce, in xmlui (tested with discovery off), view a collection page,
> then submit a new item to that collection, and go back to that collection
> page after submission. Continuously refreshing the page will not show the new
> item, unless a user tries to hard-clear the xmlui cache. Such as appending
> junk to the url as a parameter. i.e.
> servername.com/handle/123456789/1234?random-text
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.duraspace.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Forrester Wave Report - Recovery time is now measured in hours and minutes
not days. Key insights are discussed in the 2010 Forrester Wave Report as
part of an in-depth evaluation of disaster recovery service providers.
Forrester found the best-in-class provider in terms of services and vision.
Read this report now! http://p.sf.net/sfu/ibm-webcastpromo
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
