Also note that heartbeats scale very poorly. I expect large numbers of low-activity
users. Say the number of "connected" users is:
N*1000
Then the number of heartbeats with one every 5 seconds is:
N*1000/5 => N*200 per second
So I can expect N*200 requests per second when absolutely nothing is happening.
This is not a particularly good design...
> -----Original Message-----
> From: A mailing list for discussion about Sun Microsystem's Java Servlet
> API Technology. [mailto:[EMAIL PROTECTED]]On Behalf Of Chris
> Pratt
> Sent: Saturday, December 04, 1999 1:34 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [Session tracking]
>
>
> So what you're saying is that if you use a heartbeat of about 5 seconds (so
> you don't overload your network with heartbeats) and then allow the user to
> miss, oh let's say 6 heartbeats just for the sake of argument to make sure
> it's not the insanely heavy network traffic that's in the way, your user
> will be marked as go 30 seconds after his last confirmed heartbeat. Seems
> like I have the same time lag and I didn't have to do any extra programming
> to achieve it. =8^)
> (*Chris*)
>
> ----- Original Message -----
> From: "Ron Reynolds" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Saturday, December 04, 1999 6:32 AM
> Subject: Re: [Session tracking]
>
>
> > a heart-beat would do it. if, after x seconds, you don't receive a
> > heartbeat from your applet you can assume either (a) insanely heavy
> network
> > traffic, (b) client machine is unbelievably bogged down to a point where
> the
> > applet can't get a time slice, or (c) the client machine is dead and/or
> > disconnected from the network. combine that with simple ping and you can
> > even determine the difference between the browser being off and the
> computer
> > being off (again, assuming a stable, non-flooded network). (the other
> way,
> > even without power failures, is to terminate the browser process
> directly).
> > ................ron.
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
