i was thinking things would be more consistent and less confusing if we didn't use the Http* names (because they conflict with servlet API class names).
so i was thinking of renaming:
HttpRequest -> WebRequest HttpRequestCycle -> WebRequestCycle HttpReponse -> WebResponse HttpSession -> WebSession
the mock objects would stay the same since they are implementing the actual servlet API interfaces
this would have the benefit of matching the existing WebApplication class and providing easy distinctions between the Web* Wicket abstractions and the Http* servlet API stuff
any thoughts?
------------------------------------------------------- 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
