On 6/24/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
IRequestCycleFactory and ISessionFactory annoy the hell out of me. We simplified how they are used a bit in 1.3, but imho, I think we should just ditch them all together in favor of simply two factory methods in application. Factory method newSession already exists in WebApplication (as that class implements ISessionFactory), but to create a new request cycle you still have to override getRequestCycleFactory(). Objections anyone? Eelco
+1 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. -igor
