[
https://jira.duraspace.org/browse/DS-871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=19864#action_19864
]
Mark Diggory commented on DS-871:
---------------------------------
Caching needs to be better understood. Please realize that it is the earlier
pipeline stages that are determining if the pipeline should continue. Its
actually caching in all the aspects prior to the recently added transform that
need to be disabled, this includes the ArtifactViewer (or ArtifactBrowser)
aspect.
I'm generally unimpressed with the need for caching at this level. There
really is no way for any aspect to know that the stage after it will not need
to regenerate. In fact, for validation of caching to work properly all the
stages would need to be evaluated and because each stage is doing more than
just reviewing the the lastmodified timestamp on the DSO.
Finally, its rather inappropriate that the default sitemap is setting caching
no refresh http headers simply just because the item was wasn't updated. This
is another change that should have been caught and corrected in the work that
Larry did while at Harvard.
> 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
