i've got a solid sketch of page versioning and a whole bunch of related core changes i'd like to check in as a first step towards implementing verisoning and as a basis for discussion and because i don't want to get too far out of sync given the number of files i'm touching. my changes currently breaks two tests, but those problems are related to versioning itself, which isn't quite done, so that seems okay to me. the changes also remove all staleness detection and render counting from wicket, so HEAD will be somewhat broken in terms of back button support for a few days while i finish this first cut of versioning. i don't think that's /too/ far out, but i thought people would want to at least discuss this before i check things in....


thoughts?

       jon


------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop

Reply via email to