[NET-258] Implement A Keepalive Mechanism

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0
• Fix Version/s: 3.0
• Component/s: FTP
• Assignee: Unassigned
• Reporter: Rory Winston
• Created: 01/Mar/09 22:42
• Updated: 04/Jun/11 19:26
• Resolved: 02/Mar/11 19:10

Description

For routers/firewalls that terminate idle connections, a separate heartbeat mechanism may need to be implemented to keep the control connection active.

Some potential issues:

• Synchronization between a heartbeat write and a __getReply() on an active control connection command;
• Should use the NOOP command as a heartbeat signal;
• Make the timeout configurable;
• Default SocketImpl::setKeepAlive() wont do here.