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 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
use of an app in time (3 months for instance).
Of course, I can do that with variables, and build
as many different standalones as different users.
But I was wondering if there was a more general
(and more efficient) way to do that... especially
because my client isn't going to call me everytime
he needs a new copy with specific login + pwd +
time limit, and also because he isn't going to build
standalones by himself...
Thanks,
JB
_______________________________________________
use-revolution mailing list
[EMAIL PROTECTED]
http://lists.runrev.com/mailman/listinfo/use-revolution
--
Bien cordialement, Pierre Sahores
100, rue de Paris
F - 77140 Nemours
[EMAIL PROTECTED]
GSM: +33 6 03 95 77 70
Pro: +33 1 64 45 05 33
Fax: +33 1 64 45 05 33
WEB/EAI services & ACID DB over IP
"Mutualiser les deltas de productivité"
_______________________________________________
use-revolution mailing list
[EMAIL PROTECTED]
http://lists.runrev.com/mailman/listinfo/use-revolution
