[aprssig] javaprs port that doesn't send a "keepalive" packet?
Gregg Wonderly gregg at wonderly.orgWed Mar 21 13:50:01 UTC 2007
- Previous message: [aprssig] javaprs port that doesn't send a "keepalive" packet?
- Next message: [aprssig] javaprs port that doesn't send a "keepalive" packet?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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
- Previous message: [aprssig] javaprs port that doesn't send a "keepalive" packet?
- Next message: [aprssig] javaprs port that doesn't send a "keepalive" packet?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the aprssig mailing list
