Bookmark Topic Watch Topic
  • New Topic

Connection managment

 
John Burton
Greenhorn
Posts: 5
  • Mark post as helpful
  • send pies
  • Report post to moderator
I am working on an application where the main concern is speed. They are using jsf and the existing controllers are filled with multiple database calls with a connection that is being passed from call to call. It's very quick, but a complete mess with many of the same calls rewritten on every page.

I have introduced a dao layer for better maintainability and reuse, but it's just not as fast. The problem is that my connections are on a method level and creating a db2 connection is expensive. I need to create a connection and use it for all the daos in a page view. What is the best way to do that?

I was thinking of creating a DAOManager and in it's constructor having it create a connection and use the DAOMannager to get each dao and pass it the connection the constructor such as



I have not seen this documented anywhere so I am wondering if there is a better way to do it? We are not using any sort of persistence framework, just straight sql calls.

Thanks for your help!
 
Mohamed Sanaulla
Saloon Keeper
Posts: 3159
33
Google App Engine Java Ruby
  • Mark post as helpful
  • send pies
  • Report post to moderator
Please CarefullyChooseOneForum. As it looks more of a design related issue, lets continue the discussion here.
 
    Bookmark Topic Watch Topic
  • New Topic