* Jonathan Locke:
> you know, it occurs to me that this needs a lot more thought.
> maybe pages are the wrong granularity for this kind of cached
> rendering entirely. if we put this method in MarkupContainer
> instead, panels could participate enabling users to mix and
> match statefulness and caching. if you have some dynamic but
> cacheable panel that's incredibly expensive to compute, you can
> still nest it in a highly stateful page that's just normal
> wicket.
I wish to implement caching on IResourceStream, I'm not thinking
of Page or Component. Implementing caching on components does not
make sense to me, unless we can have a new kind of Component that
could produce its contents directly from an IResourceStream.
For example, a weather panel involving an HTTP request, XML
parsing and transformation is expensive to compute, but OTOH it
would be nice to have this panel embedded in a Wicket page among
other "normal" components. Thus that kind of component could me
designed as a ResourceStreamPanel that renders its content by just
copying the stream's data.
How such a component without real Markup could be part of the
rendering process?
--
Jean-Baptiste Quenot
aka John Banana Qwerty
http://caraldi.com/jbq/
