i guess you are now talking about a Component that is directly its own Resource Streamer?
of do you have Shared Resources with a detachablemodel? That would be strange because that
doesn't make anysense for wicket (we don't attach/detach it)
But for a component and a model impl that has the resource this shouldn't be a problem to begin with
Because the stream is done in one go so contenttype, data.
And last modified is not checked for those so only a last modifed request doesn't come anyway
And if it did then still we need to detach it because over request everything needs to be detached.
johan
On 2/23/06, Gili <[EMAIL PROTECTED]> wrote:
Hi,
Currently resources have no concept of the beginning or end of request
because most resources have no need for them. Problem is, if you have a
resource that is backed up by a DetachableModel there needs to be a way
to tell the model when to attach or detach itself. Currently the only
safe (but inefficient) way to do this seems to be to attach() at the
beginning of a method call and detach() at the end of it.
Ideally I'd like to give resources some sort of concept of the
beginning and end of a request so if Wicket knows it is about to query
the resource length, content-type and data I will only need to
attach/detach once across those three calls instead of three times. Is
such a thing possible or maybe you have a better idea? I can file a RFE
if needed.
Thank you,
Gili
--
http://www.desktopbeautifier.com/
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
