gnumed-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnumed-devel] Re: web frontend/patient singleton


From: catmat
Subject: Re: [Gnumed-devel] Re: web frontend/patient singleton
Date: Sun, 30 Jan 2005 17:49:10 +1100
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041231


However you can't have multiple logged-in *users*, this is nothing to do with
singletons, it's a rule of Gnumed/pycommon/gmPG.py Hacking it to allow
multiple users is certainly possible, but it all gets very complicated.
Much better to launch another process for each new user.

yes ,  gnumed uses the postgres authorization system which is sensible,
although this makes connection pooling more complicated. I haven't thought how to integrate tomcat's connection pooling with the gnumed authorization-by-connected-user , but there is a sql command "set session authorization 'username'" if the original connecting
user is a superuser, so that could be the workaround.


agreed, linux handles lots of processes easily and gmPG, gmDispatcher, gmCurrentPatient , everything,
is setup to handle just one patient at a time.
I noticed that openOffice probably forks off a new process
too ( it doesn't use a MDI frame to hold all open documents, but a new window per document).









reply via email to

[Prev in Thread] Current Thread [Next in Thread]