[Lift] Re: Thead safe part and transaction management in Lift
On Jun 24, 12:10 pm, fan...@gmail.com fan...@gmail.com wrote: Hello guys, I'm following my path through lift, and there is some part that are still not really clear for me. First question: what parts of lift are thread safe ? In particular, does the request/response handling cycle is thread safe ? I thing so, but I didn't found any doc that assert that. Yes it is thread safe. It is one of the most fundamental design scopes of lift. Do you have any specifics in mind that you need answers? Second question: how transaction are handled with Lift default ORM layout ? I'm didn't see how we declare a transaction, and especially how one can handle rollbacks. Please see DB.scala commit/rollback semantics are there. Any inputs or links toward resources answering these two points would be much appreciated ! Thanks in advance, -- Francois Armandhttp://fanf42.blogspot.com --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Lift group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: Thead safe part and transaction management in Lift
marius d. a écrit : Yes it is thread safe. It is one of the most fundamental design scopes of lift. Do you have any specifics in mind that you need answers? No, in fact I took as an assumption the thread-safety of request/response (and I saw some thread local call in the lift code), but it was to be sure :) Second question: how transaction are handled with Lift default ORM layout ? I'm didn't see how we declare a transaction, and especially how one can handle rollbacks. Please see DB.scala commit/rollback semantics are there. OK, I see the code, and I discover a buildLoanWrapper that perhaps I could call in Boot class, to have default behaviour for transaction. Thank you very much for your answers ! -- Francois Armand http://fanf42.blogspot.com --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Lift group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: Thead safe part and transaction management in Lift
On Jun 24, 2:18 pm, fan...@gmail.com fan...@gmail.com wrote: marius d. a écrit : Yes it is thread safe. It is one of the most fundamental design scopes of lift. Do you have any specifics in mind that you need answers? No, in fact I took as an assumption the thread-safety of request/response (and I saw some thread local call in the lift code), but it was to be sure :) We use thread locals quite a bit for request life cycle state management. i.e. in S object, RequestVar etc. It is a concise model of scoping state. Second question: how transaction are handled with Lift default ORM layout ? I'm didn't see how we declare a transaction, and especially how one can handle rollbacks. Please see DB.scala commit/rollback semantics are there. OK, I see the code, and I discover a buildLoanWrapper that perhaps I could call in Boot class, to have default behaviour for transaction. Thank you very much for your answers ! -- Francois Armandhttp://fanf42.blogspot.com --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Lift group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
