A couple of quick notes: On Thu, Aug 5, 2010 at 12:24 AM, Irv Wilson wrote:
> function - getuser() > lock > set userid = session.userid > /lock > return userid > 1) No lock is needed. You're simply reading from the session scope in that snippet. If you're actually doing more than that, you most likely still do not need locks, either. Bottom line: locks are a big potential for a bottleneck and should only be used if actually necessary. > I've got to say a whole lot of OO style coding > still feels to me like I'm driving around the block to go next door. > 2) When you get into the maintenance phase of your application, you will be happy as a lark that you drove around the block. It will save you loads of time on the back end. :-) -- Model-Glue Sites: Home Page: http://www.model-glue.com Documentation: http://docs.model-glue.com Bug Tracker: http://bugs.model-glue.com Blog: http://www.model-glue.com/blog You received this message because you are subscribed to the Google Groups "model-glue" 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/model-glue?hl=en
