[TIMOB-673] HTTPClient setTimeout expects array
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | Medium |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2011-04-17T01:53:52.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | Release 1.2.0 |
| Components | iOS |
| Labels | n/a |
| Reporter | Nolan Wright |
| Assignee | Blain Hamon |
| Created | 2011-04-15T02:34:09.000+0000 |
| Updated | 2011-04-17T01:53:52.000+0000 |
Description
should take single argument in milliseconds.
Comments
- Blain Hamon 2011-04-15
Sending over to Steve.
- Stephen Tramer 2011-04-15
Commit 3f54408 (not pushed): Changed -[TiNetworkHTTPClientProxy setTimeout] to use the @property interface (takes NSNumber*) as opposed to being a declared function (takes array). Has the side-effect of allowing a user to get the timeout from a client, and modify it - returns 0 if there is no current request.
- Jeff Haynie 2011-04-15
(from [3f54408e3960d0a55eb0899507a1d86b549667d6]) Closes #673 - Changed setTimeout to be a 'timeout' property. http://github.com/appcelerator/titanium_mobile/commit/3f54408e3960d0a55eb0899507a1d86b549667d6"> http://github.com/appcelerator/titanium_mobile/commit/3f54408e3960d...
- kosso 2011-04-15
What is the correct way to use this now?
Does it need setting in between open and send? Or does it get set in the HTTPClient constructor?
- Stephen Tramer 2011-04-15
Set it like you would any other property (which I believe means it can also be set in the constructor). But it must be set before opening the connection.