How can a ULC application handle server-side database connection pooling?
ULC is basically a GUI library, which takes care of client/server partitioning. Developers define the application GUI using ULC widgets and implement the application logic in the event handlers of the widgets. The connection from the application to services, databases, etc. depends on the developer’s preferences and to some extent on the container in which the ULC application is deployed. The code related to connections to databases and services can either be implemented in the container initialization-related code or in the application logic. As far as database connection pooling is concerned, one solution would be to model the pool as a singleton. The connections will be established when the first client session gets the singleton. On the other hand, if you would like to do the initialization before starting the first client session then you need to look into container facilities. ULC requires the Servlet 2.4 specification.
