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

[Dave Baxter]

I also would find it *Very* usefull to be able to at least control the "Keep alive" messages.  Every 20 or 30 seconds is way to fast, 3 to 5 minutes more like would be better, but for those of us with paid for (on a byte by byte basis) connection, the option of removing them altogether would be good.  There is usually enough other traffic to do the job.
 
Give the user the option via a "Filter" text parameter perhaps?  Keep the default as it is now, but if needed, allow the user to extend the period, or kill them altogether.
 
Tin hat is ready..
 
Dave G0WBX.
 

________________________________

From: AE5PL Lists [mailto:HamLists at ametx.com]
Sent: Tue 20/03/2007 15:18
To: TAPR APRS Mailing List
Subject: RE: [aprssig] javaprs port that doesn't send a "keepalive" packet?



TCP keep-alives were looked at but do not provide the granularity needed
for APRS-IS.  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.

73,

Pete Loveall AE5PL
pete at ae5pl.net

> -----Original Message-----
> From: Gregg Wonderly
> Posted At: Tuesday, March 20, 2007 10:09 AM
> Subject: Re: [aprssig] javaprs port that doesn't send a "keepalive"
> packet?
>
> It would seem that you could use the TCP keepalive function for this
in
> this day
> and age.  Are there specific places where TCP keepalive is not
> available and so
> you are using data instead?  I understand that there are potentially
> some broken
> clients that are taking idle time to mean lost contact.




This mail has been scanned by Palmer Cook Computer Services Limited.  www.palmercook.co.uk
-------------- next part --------------
A non-text attachment was scrubbed...
Name: winmail.dat
Type: application/ms-tnef
Size: 4807 bytes
Desc: not available
URL: <http://lists.tapr.org/pipermail/aprssig_lists.tapr.org/attachments/20070322/0f907694/attachment.dat>