| From: | Paul Thomas <paul(at)tmsl(dot)demon(dot)co(dot)uk> | 
|---|---|
| To: | Oliver Jowett <oliver(at)opencloud(dot)com> | 
| Cc: | Barry Lind <blind(at)xythos(dot)com>, Kris Jurka <books(at)ejurka(dot)com>, "pgsql-jdbc (at) postgresql (dot) org" <pgsql-jdbc(at)postgresql(dot)org> | 
| Subject: | Re: Comments on adding more connection URL parameters. | 
| Date: | 2004-02-04 09:21:42 | 
| Message-ID: | 20040204092142.A24108@bacon | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-jdbc | 
On 04/02/2004 06:04 Oliver Jowett wrote:
> [snip]
> DriverManager.getConnection() has a variant that takes a Properties 
> object, so I'd expect apps to support reading properties from a 
> configuration file to pass to the driver. Maybe it'd be preferable to 
> encourage apps to take this route rather than having a huge URL string. 
> I'm not sure we need to support passing a properties file location in 
> the URL (3) if we do this.
For web application developers who use connection pooling (e.g., me) 
passing parameters in the URL would be the preferred option. ATM, I can't 
see how putting the name of a properties file in the URL would really help 
as deciding on a valid physical location for the file can be problematic 
and is highly container-specific. For my purposes, JNDI would be 
preferable to a properties file if it is decided to add facilities beyond 
URL paramters. 
-- 
Paul Thomas
+------------------------------+---------------------------------------------+
| Thomas Micro Systems Limited | Software Solutions for the Smaller 
Business |
| Computer Consultants         | 
http://www.thomas-micro-systems-ltd.co.uk   |
+------------------------------+---------------------------------------------+
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kris Jurka | 2004-02-04 09:37:04 | Re: Comments on adding more connection URL parameters. | 
| Previous Message | Juriy Goloveshkin | 2004-02-04 08:40:31 | Re: metadata searching |