Server Sessions vs. Client Sessions?
Just wondering if anyones knows how, if possible, you could use a Server Session to work with multiple Client Sessions?
Examples: Users assigned to groups A-C (possibly ACL groups) belonging to Department I communicate with Server Session 1. Server Session 1 tracks a list of client session ids and shares with them Singleton instances, such as the registry, stored sql caches, search results, etc. User's belonging to Groups D & C belonging to Department II communicate with Server Session 2 which has different results for similar singleton types.
Users:
Sales Rep.
Sales Manager
Sales Project Manager
Belong to Group: Sales
Users:
Technical Support Analyst
TS Supervisor
TS General Manager
Belong to Group: Technical Support
So on and so forth. Sales and Technical Support will often share access to a given module (or tool) on the site. However, they will being pulling different chunks of content (results from databases, documentation, policies and procedures, etc.) If the server can maintain streamlined session instances that only cache what that single group needs and shares it amongst all the users of that department, what benefits might the application as a whole reap?
The server load can be managed by department
Server resources will be shared more efficiently with its clients
Client response times and stability should see measured improvement,
Ajax could possibly benefit by making requests that will be answered with a cached response that only has to pulled out of a locally maintained pool. The Server Session won't have to search through all of Tech Supports junk to get the results someone in Sales needs.
I invite you all to discuss possibilities or provide feedback.
Thanks
|