timeouts need to be tunable and consistent with other SDKs

Trond Norbye added a comment - 13/Nov/12 3:12 AM http://review.couchbase.org/#/c/22474

Trond Norbye added a comment - 13/Nov/12 4:17 AM The php is built on top of libcouchbase which don't expose multiple timeouts. From an operational point of view one may also question why one would want a different set of timeouts. Most applications want to have a predictable latency for the various operations, and given the distributed nature of couchbase we never know when we're going to connect to a new host (or do an auth)..

Trond Norbye added a comment - 13/Nov/12 4:26 AM The timeout values are specified in usec (just like the C library)

Matt Ingenthron added a comment - 15/Nov/12 8:25 AM Sorry for reopening, but I have two points: 1) how does someone change the timeout in libcouchbase through PHP? This is about making it reconfigurable. Maybe it is, but I don't know that we have that documented and I've not seen it. 2) The HTTP timeout for views should be 75 sec, since they can take 10s of seconds to service. Regular memcached/CRUD requests should continue with the 2.5sec timeout. Is the PHP client doing this already?

Karen Zeller added a comment - 15/Nov/12 11:31 AM My understanding is that at the C library level, there is a single timeout of 2.5 seconds. That is what I documented for PHP and C at this point for all types of server interactions (connect, CRUD, etc.)

Trond Norbye added a comment - 19/Nov/12 1:44 AM For 1: In the object oriented interface you can use: $cb->getTimeout() $cb->setTimeout(value); in the non-oo you would use: couchbase_get_timeout($cb); couchbase_set_timeout($cb, value) 2) libcouchbase don't have separate timers... if we would like different default timeouts for views we would have to add support for that...

Matt Ingenthron added a comment - 26/Nov/12 4:04 PM The view timeout is tracked in PCBC-150 , so this is closeable. See that issue for view timeout related changes on PCBC.