You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by bu...@apache.org on 2004/02/06 15:36:40 UTC

DO NOT REPLY [Bug 26725] New: - [PATCH] Improved SitemapSource

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26725>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26725

[PATCH] Improved SitemapSource

           Summary: [PATCH] Improved SitemapSource
           Product: Cocoon 2
           Version: 2.1.3
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: core
        AssignedTo: dev@cocoon.apache.org
        ReportedBy: m_rolappe@web.de
                CC: m_rolappe@web.de


the improved SitemapSource features the following:
- improve cacheability/performance by not instantly resetting and thus clearing
the SourceValidity
- instead of simply returning the mime type 'text/xml' it asks the
RedirectSource or EnvironmentWrapper (which is also patched to cache content
length, type and last modified timestamp), respectively
- returns content length and last modified timestamp, if available
- it won't simply return true on exists() but only when the pipeline processing
was successful

implementation details:
- EnvironmentWrapper is patched to store content length, content type and last
modified timestamp
- SitemapSource uses patched EnvironmentWrapper to provide the data mentioned,
this also relates to/resolves bug #25121
- SitemapSource now implements exists() dependent upon successful processing
pipeline setup/build

since my application is partly based on delegating to 'core' pipelines via the
cocoon protocol, I needed the enhancement. it increased the performance for my
use case and has been working okay for weeks now without any problems.

the patch(es) should be backportable to 2.0.x without problems.