Browse Prior Art Database

Traveling User Client Profile

IP.com Disclosure Number: IPCOM000111595D
Original Publication Date: 1994-Mar-01
Included in the Prior Art Database: 2005-Mar-26
Document File: 2 page(s) / 44K

Publishing Venue

IBM

Related People

Howell, WE: AUTHOR

Abstract

Users of Client/Server applications typically use their own client application to access the server. This client is typically resident in their work station, in their workplace. These clients are usually designed to be customized to specific preferences of the user (i.e., color, language, display layout, time-zone, application specific options, etc.). When a user has occasion to use a work station in another office, another state, or another country they are required to use the client as it is installed in that work station or use the client customization services to customize this work station to their liking.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 69% of the total text.

Traveling User Client Profile

      Users of Client/Server applications typically use their own
client application to access the server.  This client is typically
resident in their work station, in their workplace.  These clients
are usually designed to be customized to specific preferences of the
user (i.e., color, language, display layout, time-zone, application
specific options, etc.).  When a user has occasion to use a work
station in another office, another state, or another country they are
required to use the client as it is installed in that work station or
use the client customization services to customize this work station
to their liking.  This is generally tedious and time consuming, and
is most likely not done unless the user will be using the alternate
work station for an extended period or the customization is required
to receive the correct results from the server.

      A program is disclosed that will allow the user to retain their
client profile in the server and configure the client they are using
on request, or automatically each time their client binds with the
server.

      An example of an implementation would be a Calendar
client/server application.  The client would be expected to display
the calendar in a format selected by the user (i.e., Chinese,
Japanese, Gregorian, Julian, etc.).  The preference of the user can
be stored in the Calendar server, available to the Calendar client by
request of the user or automatically as part...