Exceptions enable you to detect and handle anomalous runtime conditions promptly. However, they also complicate the design of your program as they increase the number of possible execution paths. In most cases, implementing the “resource acquisition is initialization” idiom guarantees that data isn’t destroyed and that resources are always released.
Note: This tip applies primarily to UNIX platforms (fortunately or unfortunately). The code was run on a Sun Solaris server (SunOS 5.8). How many times have you wondered what programs installed on your machine will handle content of a given type? There’s an easy utility that does this called apropos.
There are instances when .jsp names need to be hidden from the URL. This can be done using various design techniques. But if your application is small and simle enough that it doesn’t even require a servlet, you can hide a real URL by defining a mapping in the web.xml
The tip “How to Force a C++ Class to Be a Singleton” does not provide enough flexibility for the programmer to control the creation/deletion of the singleton instance. The following code provides better control over memory and class instance. class MySignleton{public: static MySingleton* GetInstance() { if(!m_pThis) m_pThis = new MySingleton();
Big applications create huge numbers of objects. Though Java manages the memory allocation and de-allocation for these objects, sometimes this huge number can result in memory leak problem. To monitor when and how much garbage collection is happening, use the following example method: Suppose you start your application as: java