|
[jira] Commented: (NET-258) Implement A Keepalive Mechanism: msg#00425issues-commons-apache
[ https://issues.apache.org/jira/browse/NET-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12736189#action_12736189 ] Prasad Ganguri commented on NET-258: ------------------------------------ I would say this as a bug instead of an enhancement. This is one of the critical issues with large files for clients behind router/firewall. Please prioritize this fix. > Implement A Keepalive Mechanism > ------------------------------- > > Key: NET-258 > URL: https://issues.apache.org/jira/browse/NET-258 > Project: Commons Net > Issue Type: Improvement > Affects Versions: 2.0 > Reporter: Rory Winston > Assignee: Rory Winston > > 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. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
|
|
||||||||||||||||||||||||||
|
|
|
| News | Mail Home | sitemap | FAQ | advertise |