There's one thing that I think is important enough to put in 1.0 and could impact the archicture: the cacheability of (image) resources. I do not mean the caching of dynamically generated images that was part of the discussion earlier, but I do mean the ability for packaged (image) resources to mark themselves as cachable. For such resources, different expiry headers etc would be set, and - important - the link to those resources should be static; at least without the constantly changing pagenumber and rendercount after such a resource is requested once.

I think this is important because in my opinion the current packaged (image) resources are not useable for production systems for pages that have more than - say - five images on them. I can think of ways how to do this, but did not come up with a really elegant way yet.

Eelco


Jonathan Locke wrote:


i refactored feedback message stuff and form validation. it's quite a bit simpler and better. apologies to those whose code i broke.
i can't think of anything else i want to change at this point. i think what's left to do is mainly documentation and bug fixing. does anyone have any major complaints about the core?




-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop




-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop

Reply via email to