[aprssig] javaprs port that doesn't send a "keepalive" packet?
Gregg Wonderly gregg at wonderly.orgTue Mar 20 15:07:28 UTC 2007
- Previous message: [aprssig] javaprs port that doesn't send a "keepalive" packet?
- Next message: [aprssig] One-Wire, Opentracker troubleshoot
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
AE5PL Lists wrote: > Keep-alives on the TCP connection > are still used to ensure the client is still there. 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 would seem like a good thing to have as optional to allow these kinds of applications to be used with minimal bandwidth use. Gregg Wonderly
- Previous message: [aprssig] javaprs port that doesn't send a "keepalive" packet?
- Next message: [aprssig] One-Wire, Opentracker troubleshoot
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the aprssig mailing list
