[
https://issues.apache.org/jira/browse/SHINDIG-500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12626338#action_12626338
]
Kevin Brown commented on SHINDIG-500:
-------------------------------------
No, it's not redundant. The gadget spec factory caches parsed gadget
specifications -- rewritten content is a completely different thing, and moving
the caching logic of gadget specs into the gadget server is inflexible for
anyone who needs to produce gadget specs in a different way or who has a
different caching strategy.
Cached content is a not the same as a cached gadget spec, as not everything
that gets rewritten is a gadget spec (or even html, for that matter).
It definitely makes sense to have a separate cache for rewritten content
(assuming that rewriting is expensive and that many rewrite operations are
cacheable), but that cache should be used for *all* rewriting (the body of the
gadget, a proxied css file, or makeRequest data). The best place to put it
would probably be in the rewriter.
> Make Gadget Object's content that of the active View
> ----------------------------------------------------
>
> Key: SHINDIG-500
> URL: https://issues.apache.org/jira/browse/SHINDIG-500
> Project: Shindig
> Issue Type: Sub-task
> Components: Gadget Rendering Server (Java)
> Reporter: John Hjelmstad
> Assignee: John Hjelmstad
> Attachments: spec-immutable-notdoneyet.patch
>
>
> Step #1 of
> http://mail-archives.apache.org/mod_mbox/incubator-shindig-dev/200808.mbox/[EMAIL
> PROTECTED]
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
