You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@shindig.apache.org by "John Hjelmstad (JIRA)" <ji...@apache.org> on 2008/09/11 00:30:46 UTC

[jira] Resolved: (SHINDIG-579) Move content rewriting out of AbstractHttpCache and into code best suited to utilizing a shared rewritten-content cache

     [ https://issues.apache.org/jira/browse/SHINDIG-579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

John Hjelmstad resolved SHINDIG-579.
------------------------------------

    Resolution: Fixed

Resolved by r694035.

> Move content rewriting out of AbstractHttpCache and into code best suited to utilizing a shared rewritten-content cache
> -----------------------------------------------------------------------------------------------------------------------
>
>                 Key: SHINDIG-579
>                 URL: https://issues.apache.org/jira/browse/SHINDIG-579
>             Project: Shindig
>          Issue Type: Sub-task
>          Components: Common Components (Java)
>            Reporter: John Hjelmstad
>         Attachments: no-rewrite-in-httpcache.patch
>
>
> The fact that rewriting logic for HttpResponses currently lives in AbstractHttpCache is confusing, and the implementation of this is even worse. All notion of rewriting should be removed from AbstractHttpCache and to calling code (eg. MakeRequestHandler) which knows what rewriting semantics should apply in context.

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