On 10/10/06, Talman, Knut <[EMAIL PROTECTED]> wrote:
Why would getting the .parms files working make things worse?
Originally all of your Sun Ray DTUs always connected to one server and stayed there. Therefore all of your Sun Ray sessions were on that one server, and hotdesking would always work because the existing session was very easily found -- the session was always on the server that the DTU had connected to. Now you are using .parms files to tell the DTUs to connect to either of your two servers. Those servers do not trust each other, so they will not cooperate to locate an existing session when hotdesking is attempted. This means that your users will have an unreliable hotdesking experience. They will have two sessions, one on each server, and they will always hotdesk into the session on whichever server the DTU happens to be connected to, and that server can change each time the DTU gets restarted. If you don't care about hotdesking (maybe in your deployment you always kill a Sun Ray session when it becomes detached from a DTU) then this doesn't matter so much, although you still have a load-balancing problem because load-balancing only happens between servers that trust each other. If you do care about hotdesking then the inability to find and reconnect to an existing session on the other server is a serious problem. OttoM. __ ottomeister Disclaimer: These are my opinions. I do not speak for my employer. _______________________________________________ SunRay-Users mailing list [email protected] http://www.filibeto.org/mailman/listinfo/sunray-users
