[aprssig] javaprs port that doesn't send a "keepalive" packet?

[Matt Werner]

Perhaps being able to send the server a command (similar to a filter
command) to change the default keep-alive for that port to something
else (or 0 to shut it off)?

On 3/21/07, Gregg Wonderly <gregg at wonderly.org> wrote:
> AE5PL Lists wrote:
> > TCP keep-alives were looked at but do not provide the granularity needed
> > for APRS-IS.
>
> Is this because of TCP default timing, or something else?
>
>  > Also, there are a number of (not broken) clients that look
> > for data from the server to be assured that the connection to the server
> > is still valid.
>
> I understand that there are also clients which want "everything" and try hard to
> reestablish a new connection in the event of server malfunction (software or
> otherwise).  Because this is not a transactional system, any attempts to resolve
> the lost data problem are just best effort.  So, I am just curious what the real
> need is such that the keep alive traffic is a must have vs selectable filter.
>
> Gregg Wonderly
>
> _______________________________________________
> aprssig mailing list
> aprssig at lists.tapr.org
> https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig
>