commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Prasad Ganguri (JIRA)" <j...@apache.org>
Subject [jira] Issue Comment Edited: (NET-258) Implement A Keepalive Mechanism
Date Tue, 28 Jul 2009 18:12:15 GMT

    [ https://issues.apache.org/jira/browse/NET-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12736189#action_12736189
] 

Prasad Ganguri edited comment on NET-258 at 7/28/09 11:10 AM:
--------------------------------------------------------------

I would rather 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.

      was (Author: ganguri):
    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.


Mime
View raw message