I saw a lot of discussion of the various problems and possible
solutions but none of them was agreed upon because they each had their
own problem. All I know is that in my case the dynamically-generated
images should be treated as cacheable because they will not change with
clicks (i.e. reference count). What is the proposed solution?Gili On Tue, 04 Jan 2005 13:03:00 +0100, Eelco Hillenius wrote: >See our short discussion about this last week (the last mails of the >'Proposal for autolink replacement' thread). > >Eelco > >Juergen Donnerstag wrote: > >>sorry, but I have not experience with it. >>Juergen >> >> >>On Tue, 04 Jan 2005 02:04:13 -0500, Gili <[EMAIL PROTECTED]> wrote: >> >> >>> Just had a thought... I don't know how you guys ended up >>>designing presentation-layer components, but my round corner panel >>>generates the corner images dynamically and I wanted to ensure that the >>>images are only generated once per page, not per view. Is it up to >>>Wicket or my component to cache these images? >>> >>>Thanks, >>>Gili >>> > > > >------------------------------------------------------- >The SF.Net email is sponsored by: Beat the post-holiday blues >Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. >It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt >_______________________________________________ >Wicket-develop mailing list >[email protected] >https://lists.sourceforge.net/lists/listinfo/wicket-develop > ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
