client
object used by some of JavaScript's client-maintenance techniques.
Server-side function | |
Implemented in | Netscape Server 3.0 |
ssjs_getClientID()
project
or server
objects. In these situations, you need a way to refer uniquely to the client/application pair. JavaScript provides two functions for this purpose, ssjs_generateClientID
and ssjs_getClientID
.
Each time you call ssjs_generateClientID
, the runtime engine returns a new identifier. For this reason, if you use this function and want the identifier to last longer than a single client request, you need to store the identifier, possibly as a property of the client
object.
When you use these maintenance techniques, ssjs_getClientID
returns the identifier used by the runtime engine. Every time you call this function from a particular client/application pair, you get the same identifier. Therefore, you do not need to store the identifier returned by ssjs_getClientID
. However, if you use any of the other maintenance techniques, this function returns "undefined"; if you use those techniques you must instead use the ssjs_generateClientID
function.
If you need an identifier and you're using a server-side maintenance technique, you probably should use the ssjs_getClientID
function. If you use this function, you do not need to store and track the identifier yourself; the runtime engine does it for you. However, if you use a client-side maintenance technique, you cannot use the ssjs_getClientID
function; you must use the ssjs_generateClientID
function.
Last Updated: 10/31/97 16:38:00