[prev in list] [next in list] [prev in thread] [next in thread] 

List:       munt
Subject:    Clientname on reconnected sessions
From:       George Albertus <george.albertus () maryville ! com>
Date:       2000-05-22 16:11:01
[Download RAW message or body]

We're using the environmental variable clientname to establish a unique
device identity for client programs which need a device identifier for
printer routing and screen context. (Programs are from Shared Medical
Systems - CMS, FMS,and UCW.)

The problem arises when people disconnect from a session, then reconnect to
the same session from another device (the mobility is desirable in our
environment).  For example, someone starts a session from ThinClientA, then
launches an application which recognizes the device by name or number.  Then
they disconnect, walk to another location, and reconnect to the original
session from ThinClientB.  However the app in the session still thinks it's
ThinClientA.

The app is okay until someone steps up to ThinClientA and logs on and tries
to launch the same app, which now recognizes that there is a duplicate
request for the same device identifier, and rejects it because ThinClientA
is already in use.

Does anyone know of a way to reestablish the clientname variable with a new
device name when reconnecting to an existing session?

Thanks for your consideration,
George


George Albertus
Maryville Technologies(tm)
540 Maryville Centre, Suite 300
St. Louis, MO  63141
636/519-4159
(FAX) 636/519-4141
george.albertus@maryville.com				
www.maryville.com




--------------<< "multiuser-nt@ncd.com" FOOTER MESSAGE >>-------------------

To Unsubscribe:  Email ncd-majordomo@ncd.com with "unsubscribe multiuser-nt".
Archive of List: Use "index" and "get" commands to ncd-majordomo@ncd.com
NCD reserves the right to restrict access to this list.

[prev in list] [next in list] [prev in thread] [next in thread]