While I have worked with *nix far longer than with Windows, and absolutely agree that no one should run mission critical applications on Windows, I can't believe that native Windows games will run better under an emulation layer than under the OS they were intended for.
In my case, I like flight simulators. MS Flight Sim 2004 and X-Plane tax my 3.2ghz P4 as it is, I seriously doubt they would function very well under an emulation layer. Send me a screenshot (with all the display sliders set to max) if you are able to prove otherwise.
If the site you visit is hosted by a load balancing device but the application is not built to maintain session state between separate physical servers (most apps aren't, the developers don't ever seem to think about the fact that the app might be running in multiple places), the load balancing device must then maintain persistence of each client to the correct server for the site to work.
If you are not allowing (at least) session cookies, the load balancing device must fall back to using your source IP address to maintain persistence. If your source IP is a proxy (ie, you are an AOL user, on a corporate network, behind a gateway router, etc) then your session may be confused with another session and you may end up inside someone else's session or vice versa. I've seen this behavior on several sites where I was dumped into someone else's session with no authentication because our connections originated from the same proxy.
The way to ensure that *only* the correct client gets back into their own session is to uniquely identify them, and the easiest way to do that (without rewriting the app to use sessions in the URL) is for the load balancing device to insert a session cookie that has information on which server the client was originally load balanced to and to read that cookie on subsequent connections. The application server never even has to know about the cookie.
Therefore I submit that people's attitudes that cookies only collect/store personal information and their reaction to turn off all cookies including session cookies can actually decrease their security by exposing their sessions to access by other users.
Slashdot Mirror
Sure, everybody trusts the spammer who sends you "just one" email to take you off his list when you reply, right? Right.
I say more power to those who are pushing for zero tolerance.
DennyWhile I have worked with *nix far longer than with Windows, and absolutely agree that no one should run mission critical applications on Windows, I can't believe that native Windows games will run better under an emulation layer than under the OS they were intended for.
In my case, I like flight simulators. MS Flight Sim 2004 and X-Plane tax my 3.2ghz P4 as it is, I seriously doubt they would function very well under an emulation layer. Send me a screenshot (with all the display sliders set to max) if you are able to prove otherwise.
DennyIf the site you visit is hosted by a load balancing device but the application is not built to maintain session state between separate physical servers (most apps aren't, the developers don't ever seem to think about the fact that the app might be running in multiple places), the load balancing device must then maintain persistence of each client to the correct server for the site to work.
If you are not allowing (at least) session cookies, the load balancing device must fall back to using your source IP address to maintain persistence. If your source IP is a proxy (ie, you are an AOL user, on a corporate network, behind a gateway router, etc) then your session may be confused with another session and you may end up inside someone else's session or vice versa. I've seen this behavior on several sites where I was dumped into someone else's session with no authentication because our connections originated from the same proxy.
The way to ensure that *only* the correct client gets back into their own session is to uniquely identify them, and the easiest way to do that (without rewriting the app to use sessions in the URL) is for the load balancing device to insert a session cookie that has information on which server the client was originally load balanced to and to read that cookie on subsequent connections. The application server never even has to know about the cookie.
Therefore I submit that people's attitudes that cookies only collect/store personal information and their reaction to turn off all cookies including session cookies can actually decrease their security by exposing their sessions to access by other users.
Denny