Subtitles of the Movie

I thought it valuable for you to have some recommendations with regards to locking, so I have a little list here that you can follow. Look over your code to determine if locking should be done, especially if you're using an application or session-scope variable. Consider using a lock when you need to write to a variable. Minimize locking however. It does slow down performance. Only add a lock if the data could be affected by multi-threading. Multiple-page requests, trying to change the value at the exact same time. Don't put queries or other time-consuming code into a lock. If you do, you will find that your code and your performance is drastically undermined, so that is something to avoid. Use named locks instead of scope locks as much as you can. Just be cautious in naming your locks. Make sure you add the application name to a named lock so that multiple applications on the same server don't end up locking accidentally. Also, it is something to keep in mind that you can end up using the same name within your application for a lock and those two would end up waiting for one another, so just be cautious when you're using a named lock. And do not nest locks. The Adobe recommendation is that you do not nest locks. You may read books otherwise, but that is the preferred standard. You can run into a deadlock if you accidentally nest your locks in the wrong manner. One lock is waiting for the other to release, the other is waiting for this one to release and you get what's called a deadlock and your entire code freezes up. So that is not a situation you want to be in, so do not nest locks. And we'll be using locks coming up later in the course, so as you can see, we didn't really get into the code and type it out and all of that. We'll be doing that coming up. I just wanted to give you a good basis for locks and the information involved in them right now so that later when I'm using them, I don't have to go through all these explanations.