[deletia] > My second question is isn't it true that, assuming all other things > being equal, any algorithm or function coded in binary, compiled > language is going to perform better than one written in a markup > language and executed in JIT or even an interpreted language > executed in > a virtual machine?
Agreed, but once again I come back to the concept that the compiler, no matter how fast, may not lock as effeciently as the developer does. [deletia] > > It would be very difficult to make a system smart enough to know > > "Hey, I could use one lock around this particular block of code." > > Therefore, we would be stuck with the slower alternative. > > What you neglect to mention is that when you lock access to a session > variable, you lock access to all session variables, causing other, > potential more common and severe performance problems, especially in > regards to the "Application" scope. Like what? Also, there are different kinds of locks. You only block access to the scope during an exclusive lock. Most situations will have code that is written rarely and read often. [deletia] > Coding three lines of code to every one reference to a shared scope, > inventing workarounds (i.e. synchronizing all the data to the Request > scope or storing serialized session data in client variables) > is not my > idea of RAD. In fact, I would say it is the exact opposite. I disagree, but, I'm getting the idea this is like religion and we won't convince each other. ;) I _truly_ think people here are underestimating the complexity of auto locking inside the server. -rc ______________________________________________________________________ Get the mailserver that powers this list at http://www.coolfusion.com FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
