On Dec 31, 2009, at 11:55 AM, Marius wrote: > On Dec 31, 6:47 pm, Ross Mellgren <[email protected]> wrote: >> On Dec 31, 2009, at 11:39 AM, Marius wrote: >> The only problem I thought of when I was thinking about this earlier >> is that LiftSession.contextPath can be calculated in the absence of >> an >> obvious Req (which is presumably why LiftRules.calcContextPath takes >> LiftSession, versus calculateContextPath that takes HTTPRequest?). >> Would you solve it by just making it use S.request? I'm asking more >> for my own curiosity than anything else. > > Not sure, it might be the case. However when we construct a > LiftSession we provide the contextPath from the request and that is > retained in the LiftSession, meaning that the contextPath can be > safely obtained even if a request is not around ... say from a > CometActor.
Thanks. I'm still trying to get a solid handle on how the Lift request processing pipeline works on the inside, every piece helps! -Ross -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/liftweb?hl=en.
