I will take this question off-line. If anyone else is interested,
let me know separately so that we do not clog up this list.
-Mike
At 07:05 AM 9/4/97 -0400, Eric V. Smith wrote:
>On Thursday, September 04, 1997 12:48 AM, Micheal Sean [SMTP:padre @
Ivy .
NET]
>wrote:
>>
>> What udp apps do you deal with ? dns and ntp. These aren't major
>> bandwidth hogs. In fact, lookups are tcp. What's nice about the
>> local director is between 45 and 90 Mbs throughput and true fault
>> tolerance (HSRP). That and the fact that NO client or server
>> side software installation is needed.
>
>This is a LocalDirector question and isn't really related to firewalls, so
>I apologize in advance.
>
>I have a client who wants to use a LocalDirector to balance load across
>multiple web servers. The problem is that they are maintaining state on
>the servers, using cookies sent back to the clients to manage which state
>information belongs to which client. If you're familiar with Microsoft ASP
>sessions, it's the same thing. The upshot is that every request from a
>given client must go to the same server. Does anyone know if the
>LocalDirector can handle this? There would be an idle timeout of say 20
>minutes after which a request from the same client would be considered a
>new session, so it wouldn't have to have infinite memory to remember every
>client connection ever made.
>
>Here's the firewall slant: I'm concerned that even if the LocalDirector
>can do this, outbound HTTP proxies at the client would cause everyone from
>AOL, for example, to hit the same web server.
>
>Has anyone ever tried using a LocalDirector for this application?
>
>Thanks.
>
>Eric.
>
>
>
______________________________________________________________________
Mike Tibodeau, Systems Engineer, Cisco Systems, Inc., Herndon, VA.
Well, if you're like me, and I know I am...
References:
|
|
