What is the best way to implement such a daemon?

S

sitev_ru2015-03-24 13:52:56

Java

sitev_ru, 2015-03-24 13:52:56

I want to write a demon so that it connects to the database and keeps the connection. Now we connect to the daemon from the web page, exchange data through the connection, disconnect ... But we continue to keep the connection to the database ...
Advise how best to implement such a daemon?
Please help me with the name...

Reply

Answer the question

In order to leave comments, you need to log in

4 answer(s)

P

protven, 2015-03-24
@protven

You, judging by the description, came up with the Connection Pool. No need to write it yourself, look towards ready-made implementations. BoneCP, Tomcat connection pool, etc.

S

SaertiS, 2015-03-24
@SaertiS

roam the ConnectionPool.

V

Vitaly Pukhov, 2015-03-24
@Neuroware

If there is a similar "daemon" in the C# context, the server application that listens on the port and redirects requests received through the port to the database side and returns the response back, did it for the sake of interest as a kind of "SQL proxy". Easily implemented due to Remoting technology

S

sitev_ru, 2015-03-24
@sitev_ru

Can I set up such a Connection Pool so that only one connection to the database is opened for one browser session?