|
|||||||||
|
|||||||||
| |||||||||
|
|||||||||
|
|||||||||
| |||||||||
|
|
|
| |||||||||
 |
|
|
«
Previous Thread
|
Next Thread
»
|
Thread Tools | Search this Thread | Rate Thread | Display Modes |
Dev Shed Forums Sponsor:
|
|
Get inside! Sample the range of functionality easily built with JMSL Library for Time Series Data Analysis, Heat Maps, Portfolio Optimization, Monte Carlo Simulation, Stock Price Charting and more. Download Now! |
|
#1
July 17th, 2003, 10:06 AM
|
|||
|
|||
|
server farms & sessions
Has anyone used any session replacment components for use in a server farm environment?
I've seen the XML COM+ Session replacement object. Has anyone used it? With success? Any alternatives? Thanks!
|
|
#2
July 17th, 2003, 11:09 PM
|
|||
|
|||
|
Are you wanting to allow multiple servers to recognize other servers session identifiers?
|
|
#3
July 18th, 2003, 07:50 AM
|
|||
|
|||
|
Exactly.
We want our application to be scalable to any number of web servers at some point. Regular ASP session variables exists only one 1 server, so if the client is sent to another server, the session is lost. I wanted to explore a session replacement component first, before examining a way to keep a user on 1 server for the whole session. any ideas or tricks you've tried that you can help me with? thanks!
|
|
#4
July 18th, 2003, 06:32 PM
|
|||
|
|||
|
You could try using one central logon server and supplying the user with some form of authentication, most likely a cookie of some sort. The individual servers are able to communicate with the logon and validate the user's authentication and update if necessary.
|
|
| Viewing: Dev Shed Forums > Programming Languages - More > ASP Programming > server farms & sessions |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|
 |
|
|
Del.icio.us
Digg
Google
Spurl
Blink
Furl
Simpy
Y! MyWeb
Linear Mode
