You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@couchdb.apache.org by Apache Wiki <wi...@apache.org> on 2010/05/07 20:29:00 UTC

[Couchdb Wiki] Update of "HTTP_database_API" by SebastianCohnen

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Couchdb Wiki" for change notification.

The "HTTP_database_API" page has been changed by SebastianCohnen.
The comment on this change is: added note about configured maximum used by timeouts for changes feeds.
http://wiki.apache.org/couchdb/HTTP_database_API?action=diff&rev1=21&rev2=22

--------------------------------------------------

  ||''since''||seqnum||''0''||Start the results from the change immediately after the given sequence number.||
  ||''feed''||normal | longpoll | continuous||''normal''||Select the type of feed.||
  ||''heartbeat''||milliseconds||''60000''||Period in milliseconds after which a empty line is sent in the results. Only applicable for ''longpoll'' or ''continuous'' feeds. Overrides any ''timeout''.||
- ||''timeout''||milliseconds||''60000''||Maximum period in milliseconds to wait for a change before the response is sent, even if there are no results. Only applicable for ''longpoll'' or ''continuous'' feeds.||
+ ||''timeout''||milliseconds||''60000''||Maximum period in milliseconds to wait for a change before the response is sent, even if there are no results. Only applicable for ''longpoll'' or ''continuous'' feeds. '''Note''' that 60000 is also the default maximum timeout to prevent undetected dead connections.*||
  ||''filter''||designdoc/filtername||''none''||Reference a filter function from a design document to selectively get updates. See the [[http://books.couchdb.org/relax/reference/change-notifications|section in the book]] for more information.||
  ||''include_docs''||boolean||''false''||Include the associated document with each result. (New in version 0.11)||
+ 
+ * You can change the default maximum timeout in your ini-configuration:
+ {{{
+ [httpd]
+ changes_timeout=#millisecs
+ }}}
  
  By default all changes are immediately returned as a JSON object: