couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jan Lehnardt (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (COUCHDB-1099) Does Chrome/Chromium have a problem with long polling?
Date Sat, 16 Apr 2011 21:36:05 GMT

     [ https://issues.apache.org/jira/browse/COUCHDB-1099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jan Lehnardt closed COUCHDB-1099.
---------------------------------

    Resolution: Not A Problem

This is not a CouchDB issue, closing.

(This is relevant to CouchDB users, so thanks for raising, but there's nothing we can do about
it :)

> Does Chrome/Chromium have a problem with long polling?
> ------------------------------------------------------
>
>                 Key: COUCHDB-1099
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-1099
>             Project: CouchDB
>          Issue Type: Question
>          Components: HTTP Interface
>    Affects Versions: 1.0.1, 1.0.2
>         Environment: Chromium 12.0.707.0 (78659) Ubuntu 10.10
>            Reporter: Murphy McMahon
>            Priority: Minor
>              Labels: ajax, chrome, chromium, longpolling
>
> When sending asynchronous long polling requests to CouchDB's _changes feed, Chromium's
loading indicator never stops spinning. This gives the user the impression that the webpage
is not ready to be used.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message