Hi there,
I come from a client/server world where every one has an inidividual database login on an application.
Now, in n-tier, I have seen a lot of apps using only a single DB connection behind the seen (simulating user login in the applciation with a users table, whatever).
This sounds ugly to me to have everybody using the same DN cnx because it spoils all the security, audit, ... features of the database login.
For an intranet site, is there any clear bar on making a separated DB connection for each user (ie. web session) ?
thx
I come from a client/server world where every one has an inidividual database login on an application.
Now, in n-tier, I have seen a lot of apps using only a single DB connection behind the seen (simulating user login in the applciation with a users table, whatever).
This sounds ugly to me to have everybody using the same DN cnx because it spoils all the security, audit, ... features of the database login.
For an intranet site, is there any clear bar on making a separated DB connection for each user (ie. web session) ?
thx