the reason is that we are exposing the fact that there is a stack. if we wanted to reimplement this later without a stack we would not be able to without api breaks. i dont feel strongly about it because i dont think we are likely to reimplement the thing, so do whatever you want.
-igor On Fri, Dec 17, 2010 at 8:45 AM, Jeremy Thomerson <[email protected]> wrote: > On Fri, Dec 17, 2010 at 12:28 AM, Igor Vaynberg > <[email protected]>wrote: > >> why? >> > > Someone asked me about it, and although I think there are better ways, I > couldn't see a reason that we shouldn't allow access, and wondered what > others thought. The reason was for some kind of in-depth request logger > that could log not only what was originally requested, but what eventually > actually ended up being the response. i.e., look at the request target > stack and see that the original request target was a form submission on page > X, and last target was a page request target for Y, or a download target, > etc.... > > > -- > Jeremy Thomerson > http://wickettraining.com > *Need a CMS for Wicket? Use Brix! http://brixcms.org* >
