[
https://issues.apache.org/jira/browse/AXISCPP-526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nadir amra updated AXISCPP-526:
-------------------------------
Summary: Add ability to specify connect timeout (was: Response timeouts in
addition to connection timeouts)
> Add ability to specify connect timeout
> --------------------------------------
>
> 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 <[email protected]>
> > 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 <[email protected]>
> > 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 <[email protected]>
> > 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 <[email protected]>
> > >
> > > 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 <[email protected]>
> > > 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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
