by
Dean Cooper >> Tue, 7 Dec 1999 3:50:57 GMT
Yes, but aren't there other differences too... in regards to performance. JADE makes certain assumptions when deployed that are different from when in development mode. Perhaps Dean can enlighten us further...
I assume you're referring to production mode, Craig. Production mode can be enabled in both development and deployment databases using jdbutil.exe in Jade 5, or jadload.exe in Jade 4. It is generally of use only when you put an app into production (in either a deployment or development db). When production mode is enabled, the mechanism the kernel uses to acquire and release classes at the server is slightly different. The acquire/release mechanism is what allows the kernel to keep track of all of the nodes and processes that have a particular class in use. In non-production (ie: development) mode, classes are acquired and released individually when they are opened and closed, and they can be closed more frequently depending on what you're doing in development. Each class open/close requires a communication with the server. In production mode, when a process starts we acquire the whole schema from which it is running, and when a process ends we release the schema. An acquired schema implies that all of the classes in that schema (and its superschemas) are in use. In production mode, there is no acquisition/release communication with the server per class; only per process when it starts and finishes. This can improve the speed of operations that need to open a lot of classes (eg: application start up).
Because production mode causes entire schemas to be acquired (ie: registered as in use) and released, it is not recommended that you enable production mode in your development databases. If you bring up the Jade 5 development environment against a production mode database, you'll be given a warning message (Jade 4 doesn't give you a warning).
A couple of other effects of enabling production mode are that the User Interrupt window is not shown, and the default exception handler dialog does not allow exceptions to be continued (the Ignore button is always disabled).
Note: In Jade 4, production mode is set per application. In Jade 5, it is set for the entire database. If you're going to enable production mode in a Jade 4 system, ensure that it is enabled for *all* applications that you're going to run. You can encounter problems running a mix of production and non-production in the same system. Jade 5 eliminates this problem as production mode is a system-wide setting.
Dean.