[ale] reasonable socket life

[Greg Freemyer]

I've got a project with upto 800 connections across the country.  We
close all the sockets every night as a just in case.  They only get
reopened if their is user activity at the field location.

We use to not do that, but we would get weird issues.  We tried
heartbeats etc. but it was very hard to do and never as reliable as we
hoped.

Since going to a nightly closing of the sockets, the network seems
more reliable.

Greg

On Wed, Mar 4, 2009 at 11:03 AM, Atlanta Geek <atlantageek at gmail.com> wrote:
> Quick poll/question.
> Assume you have a daemon that talks to another daemon across a network
> over a socket.  The communication is constant and unlike http requests
> are always alive. These socket connections would be across a multimile
> geographic area but within a corporate WAN.
> How often would you expect a connection would need to be restarted
> before you decide that the connection is unstable. hours,
> weeks,months? Please don't say seconds.
>
> --
> http://www.atlantageek.com
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> http://mail.ale.org/mailman/listinfo/ale
>



-- 
Greg Freemyer
Litigation Triage Solutions Specialist
http://www.linkedin.com/in/gregfreemyer
First 99 Days Litigation White Paper -
http://www.norcrossgroup.com/forms/whitepapers/99%20Days%20whitepaper.pdf

The Norcross Group
The Intersection of Evidence & Technology
http://www.norcrossgroup.com