Igor Vaynberg wrote:
also what to do about session.newrequestcycle vs
application.newdefaultrequestcycle. can we get rid of the session one? i
understand the "concept" of a cascade: application creates session, session
creates request cycle. but how practical is that? when do you want
different
request cycles for different sessions? and we already do create
request/response in application where if you would follow the cascade idea
they should be created in requestcycle, so its kinda broken already
anyways.
Yeah. If you're fussed you can have some simple switch logic in
application#newRequestCycle().
It's a sufficiently uncommon case that we definitely shouldn't be
complicating the API due to it.
+1 on:
- Ditch ISessionFactory, leave Application#newSession()
- Ditch IRequestCycleFactory, create Application#newRequestCycle()
- Ditch Session#newRequestCycle(), no replacement.
Regards,
Al
--
Alastair Maw
Wicket-biased blog at http://herebebeasties.com
