RE: Client variables

Scott Helm Mon, 17 Jul 2000 14:47:24 -0700

Title: RE: Client variables

The sticky sessions option is what we were looking at before, however
if you use an absolute url reference, like https://whatever.com, ClusterCats
sends it back to the cluster entry point and you are no longer guaranteed to
go back to the server you were on.

Thanks!

Scott Helm
[EMAIL PROTECTED]

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Monday, July 17, 2000 4:42 PM
To: [EMAIL PROTECTED]
Subject: RE: Client variables

Another possibility is to use "sticky" sessions. When a user enters your
site, they will stay on the same server for the entire session. This
approach does have its disadvantages, but it may be easier to implement
(especially since client variables by default can't handle arrays or
structures).

-----Original Message-----
From: Scott Helm [mailto:[EMAIL PROTECTED]]
Sent: Monday, July 17, 2000 2:56 PM
To: '[EMAIL PROTECTED]'
Subject: RE: Client variables

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01BFF020.A183F464
Content-Type: text/plain;
charset="iso-8859-1"

Thanks for the fast reply. I think I *have* to do something gross like
recasting ally my vars from session to client. Do client varibles have the
ability to store arrays or structures?

Thanks!

Scott Helm
Ballantyne Consulting Group
[EMAIL PROTECTED]

-----Original Message-----
From: robi sen [mailto:[EMAIL PROTECTED]]
Sent: Monday, July 17, 2000 2:00 PM
To: [EMAIL PROTECTED]
Subject: Re: Client variables

Session vars are srictly mem based and should not be used in situations
where you are trying to share state amongst a number of machines. You
could do somehting grosse like recast all your vars as need from session
to client but what would be better is to just use client vars in the
sections where you need to share state.

------_=_NextPart_001_01BFF020.A183F464
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2448.0">
<TITLE>RE: Client variables</TITLE>
</HEAD>
<BODY>

Thanks for the fast reply.  I think I *have* to =
do something gross like recasting ally my vars from session to =
client.  Do client varibles have the ability to store arrays or =
structures?

Thanks!

Scott Helm
 Ballantyne Consulting Group
 [EMAIL PROTECTED]

-----Original Message-----
 From: robi sen [<A =
HREF=3D"mailto:[EMAIL PROTECTED]">mailto:[EMAIL PROTECTED]</A>]
 Sent: Monday, July 17, 2000 2:00 PM
 To: [EMAIL PROTECTED]
 Subject: Re: Client variables

Session vars are srictly mem based and should not be =
used in situations
 where you are trying to share state amongst a number =
of machines.  You
 could do somehting grosse like recast all your vars =
as need from session
 to client but what would be better is to just use =
client vars in the
 sections where you need to share state.

</BODY>
</HTML>
------_=_NextPart_001_01BFF020.A183F464--
----------------------------------------------------------------------------
--
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/spectra_talk
or send a message to [EMAIL PROTECTED] with
'unsubscribe' in the body.

------------------------------------------------------------------------------
To Unsubscribe visit http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/spectra_talk or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body..

RE: Client variables

Reply via email to