Re: Packaging of a Web viewer of medical images
Thanks for your hints! I only have basic knowledge of PostgreSQL.
I followed both of your suggestions: Advisory locks are now used instead of setting values in a table of global properties , and connection URIs can be used instead of specifying explicit authentication options .
----- Mail original -----
> De: "Karsten Hilbert" <Karsten.Hilbert@gmx.net>
> À: email@example.com
> Envoyé: Mercredi 25 Février 2015 22:18:15
> Objet: Re: Packaging of a Web viewer of medical images
> On Wed, Feb 25, 2015 at 04:32:17PM +0100, Sébastien Jodogne wrote:
> > please note that official PostgreSQL support is now also available
> > for Orthanc .
> For what it is worth I'd suggest to support connection URIs
> rather than single explicit authentication options (host,
> port, user, ...) in the config file.
> That way you can have the user supply the full authentication
> requirements and treat it as an opaque string as far as
> Orthanc is concerned. All it does is pass it on to libpq and
> there's no need to worry about ipv4/ipv4/ports/UNIX domain
> sockets/trust/peer/md5/ssl/kerberos/gssapi/whatnot types of
> authentication which are all available with PostgreSQL.
> Unless, of course, you need to _know_ about certain parts of
> the authentication token inside Orthanc in order to process
> them (host, user, ...).
> GPG key ID E4071346 @ eu.pool.sks-keyservers.net
> E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
> To UNSUBSCRIBE, email to debian-med-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
> [🔎] 20150225211815.GB2504@hermes.hilbert.loc">https://lists.debian.org/[🔎] 20150225211815.GB2504@hermes.hilbert.loc