From c-dev-return-22053-apmail-axis-c-dev-archive=axis.apache.org@axis.apache.org Tue Mar 29 22:51:48 2011 Return-Path: Delivered-To: apmail-axis-c-dev-archive@www.apache.org Received: (qmail 81018 invoked from network); 29 Mar 2011 22:51:47 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 29 Mar 2011 22:51:47 -0000 Received: (qmail 88016 invoked by uid 500); 29 Mar 2011 22:51:47 -0000 Delivered-To: apmail-axis-c-dev-archive@axis.apache.org Received: (qmail 87924 invoked by uid 500); 29 Mar 2011 22:51:46 -0000 Mailing-List: contact c-dev-help@axis.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache AXIS C Developers List" Delivered-To: mailing list c-dev@axis.apache.org Received: (qmail 87916 invoked by uid 99); 29 Mar 2011 22:51:46 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 Mar 2011 22:51:46 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED,T_RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 Mar 2011 22:51:43 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id D23518659E for ; Tue, 29 Mar 2011 22:51:05 +0000 (UTC) Date: Tue, 29 Mar 2011 22:51:05 +0000 (UTC) From: "nadir amra (JIRA)" To: c-dev@axis.apache.org Message-ID: <127879759.20112.1301439065857.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (AXISCPP-526) Response timeouts in addition to connection timeouts MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/AXISCPP-526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012758#comment-13012758 ] nadir amra commented on AXISCPP-526: ------------------------------------ Forgot to add the the current implementation does have support for a response time-out. What is still to do is add support for a connect timeout. > Response timeouts in addition to connection timeouts > ---------------------------------------------------- > > Key: AXISCPP-526 > URL: https://issues.apache.org/jira/browse/AXISCPP-526 > Project: Axis-C++ > Issue Type: Improvement > Components: Transport (Client) > Affects Versions: current (nightly) > Reporter: Tim Bartley > > It would be highly useful to be able to specify an independent response timeout in addition to the connection timeout currently specifiable. > The following e-mail chain records a discussion from the user list about this: > > > > Tim Bartley > > 24/02/2005 23:34 > > Subject > > > > Re: Connection timeout vs response timeout? > > > > > > Right and I would see a response timeout as applying between each > > chunk as well as before the first chunk. Now there may be some > > strange applications that try and stream data in a slow response e. > > g. send one array element every minute as a stock ticker, I've seen > > horrible HTTP apps like that but they're the very sparse exception > > rather than the rule. > > > > Regards, > > > > Tim > > -- > > IBM Tivoli Access Manager Development > > > > Samisa Abeysinghe > > 24/02/2005 21:15 > > > > Subject > > > > Re: Connection timeout vs response timeout? > > > > > > As per the pull model used in Axis C++, it starts parsing the message > > as soon as some part of the message is received. Hence it would make > > more sense to time out on first byte arrival. > > However, if a message is partially dealt with the pull parser, and the > > other part does not arrive (or too late), there has to be mechanisms > > to deal with that as well. > > > > Samisa... > > > > > > On Thu, 24 Feb 2005 10:00:36 +0000, John Hawkins wrote: > > > > > > What do exactly do we mean by response timeout - is it the time before the > > > first byte comes back across the wire? Or the time for the whole msg to get > > > back ? > > > > > > > > > Samisa Abeysinghe > > > > > > 24/02/2005 01:35 > > > SubjectRe: Connection timeout vs response timeout? > > > > > > Hi Tim, > > > As of now, we have only the concept of connection timeout. > > > It is not defined what would happen if a response gets delayed. > > > Sounds to me it is a good idea to look into this. > > > > > > Thanks, > > > Samisa... > > > > > > > > > On Thu, 24 Feb 2005 10:08:50 +1000, Tim Bartley > > > wrote: > > > > > > > > Hi, > > > > > > > > On the client side, are connection timeouts able to be controlled > > > > indpendently of response timeouts? > > > > > > > > I commonly want a short connection timeout but a longer responsetimeout - > > > > if connection is going to fail I want to know quickly and failover but I'm > > > > happy to wait sufficient time for the response to actually be generated. > > > > > > > > Thanks, > > > > > > > > Tim > > > > -- -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: c-dev-unsubscribe@axis.apache.org For additional commands, e-mail: c-dev-help@axis.apache.org