the server side is a VERY good suggestion, since the
app is useless without online connection...
Thank you all,
JB
> > One way:
> > If the app *requires* access to the Web, you could maintain a list of
> > users
> > and their privileges on the server. Just make sure to allow for local
> > runnin
One way:
If the app *requires* access to the Web, you could maintain a list of
users
and their privileges on the server. Just make sure to allow for local
running of the app without the access list if the app is permitted to
do so.
This would be my suggestion also, with one suggestion if the app
The best is to handle this on the server side, inside a postgresql
authentification table. I use this way all the time to manage
"login/password" protected accesses to all of my networked n-tier apps.
Best, Pierre
Le 7 sept. 04, à 21:34, jbv a écrit :
Folks,
One of my clients wants a webapp with
Recently, "jbv" wrote:
> One of my clients wants a webapp with a large
> set of functions, and he's gonna distribute them
> to his colleagues, but needs to enable / disable
> certains functions, differently for each user.
> He also wants a login & pwd for each user (that
> will be entered at star
Folks,
One of my clients wants a webapp with a large
set of functions, and he's gonna distribute them
to his colleagues, but needs to enable / disable
certains functions, differently for each user.
He also wants a login & pwd for each user (that
will be entered at start up) and possibly limit the
