H
HPDBA
Guest
Currently, openAccess loads the ip jar file once a client tries to connect. It the loads the IP jar file and calls ipConnect. The JVM that is loaded is shared by all connections. However, since the first call to the IP is ipConnect, the IP doesn't have any chance of doing any initialization before a user logs in. This is unfortunate! In our use case, we have a LOT of information to process and load into memory before the users are presented with their 'database'. So, the first user to login pays the (huge) penalty - along with any users that login before the initialization is done. What would be better would be for the OA server to load the IP upon start up, and then call a new API routine, such as ipInitialize to allow the IP a chance to begin initialization before any users log in. If an implementation of the IP doesn't want/need to do any initialization, they can simply leave the routine empty.
Continue reading...
Continue reading...