How to manage access to jsps in ur application?

Question

Hi!
we are developing J2ee application in which we have many Jsp pages , these jsp pages are accessed by different clients in different modes (i.e if administrator is watching a page then all the facilities in page will be available to him but if any other user is watching the same page then he will not be able to use all of it's functionalaty ).
Now problem comes if many user (let say 100-200) user accessing same page (in different modes) i.e single source is beeing accessed by multiple clients ...then performance issue will accour here coz we are not managing this resource properly(Like we do pooling of database connections if we know that many user will access the database and they will need database many connections ...tis way only 10 connection objects can handel 100 clients accessing the database).
one of out team members has given the idea of putting same jsps(with same logic but different name)in different folders...like for addministrator we will have administrator folder in which we put all those jsps that he can access then again for any other class of users let say clerk we will have a folder named clerk having all thos pages which he may need(note that there may be same pages with different names in last two folders)....this way only the page for clerk class is loaded(from clerk folder) and if administrator wants to access the same page it will be loaded from his directory.......
but i am not satisfied with this approach as there should any better approach for resource managment of jsps and doing reaserch on it ......
If any one on this forum has any idea about that then plz help me
thanx in advance
sajjad ahmed paracha

Answer 1

Doesn't matter.
You'd still get the same number of requests which is your real problem.
It might make sense to group your JSPs in subfolders dividing them up for functionality but that's only for ease of organisation (maybe you want access control on such directories for example).
What you really need to do is get those connection pooling and stuff under control and properly configure your application and database servers to function under high load.
This might mean you will have to think about clustering the entire application across multiple servers but with 100 clients that should not be needed.
You might also have to look at the efficiency of your SQL queries. Do some take an inordinate amount of time to complete or return far more data than is needed?
If so see if you can optimise them. Maybe placing some indices on often used database tables will speed things up a lot as well.
Maybe some queries are performed a lot but the results are pretty much always the same? Consider caching those results and performing the actual query only once every hour or day (depending on how often the data changes).
Talk with your DBAs about tracing SQL.