[PCBC-190] Need documentation on timeouts available for PHP Created: 29/Jan/13  Updated: 27/Sep/13  Resolved: 27/Sep/13

Status: Resolved
Project: Couchbase PHP client library
Component/s: docs
Affects Version/s: 1.1.2
Fix Version/s: 1.2.0
Security Level: Public

Type: Bug Priority: Major
Reporter: Perry Krug Assignee: Brett Lawson
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
This link: http://www.couchbase.com/docs/couchbase-devguide-1.8/about-client-timeouts.html, states that there aren't any timeouts available for PHP

The PHP docs don't describe any.

However, I know that the underlying libcouchbase exposes at least one basic request timeout setting so either the PHP library needs some help exposing that, or it already does and we need to document it.

 Comments   
Comment by Matt Ingenthron [ 15/Apr/13 ]
Trond: Could you please review the existing documentation, recommend where we should put this information, then write up a draft and assign it back to me? Then I can review and get it over to Karen.

Let's try to do this one very soon.
Comment by Trond Norbye [ 16/Apr/13 ]
    /**
     * Retrieve the current operation timeout.
     *
     * @return integer The currently used timeout specified in usec
     */
    function getTimeout() {

    }

    /**
     * Specify an operation timeout.
     *
     * The operation timeout is the time it takes from the command is sent
     * to the cluster and the result should be returned back.
     *
     * @param integer $timeout the new operation timeout specified in usec
     */
    function setTimeout($timeout) {

    }

The keyDurability methods have a timeout parameter, and the view have the connection_timeout parameter one may set.
Comment by Perry Krug [ 16/Apr/13 ]
Thanks Trond. A few more questions:

-This bug was specifically requested for PHP...can you provide documentation on how to exercise those timeouts through PHP?
-And is there a separate timeout associated with the initial connection to 8091?
-Is there any logic/handling of a case where the comet stream becomes un responsive but is not actually reset?
Comment by Matt Ingenthron [ 25/Sep/13 ]
Brett: with your recent docs work, you can probably work out what is best for this.
Comment by Brett Lawson [ 27/Sep/13 ]
Added section to documentation.
https://github.com/couchbaselabs/docs-ng/commit/e5942bbcc1c3414b4698799319beed18b41448de
Generated at Tue Jul 29 10:48:10 CDT 2014 using JIRA 5.2.4#845-sha1:c9f4cc41abe72fb236945343a1f485c2c844dac9.