Last modified: 2014-06-06 02:58:10 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T68232, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 66232 - RCStream: Upgrade backend to use protocol that works with socket.io 1.0.x
RCStream: Upgrade backend to use protocol that works with socket.io 1.0.x
Status: ASSIGNED
Product: Wikimedia
Classification: Unclassified
Stream (Other open bugs)
wmf-deployment
All All
: High enhancement (vote)
: ---
Assigned To: Ori Livneh
https://github.com/abourget/gevent-so...
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2014-06-06 00:58 UTC by Krinkle
Modified: 2014-06-06 02:58 UTC (History)
2 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Krinkle 2014-06-06 00:58:35 UTC 
When using socket.io.js from 1.0.x, no connection can be established.

The client is trying to make connections to

http://stream.wikimedia.org/socket.io/?EIO=2&transport=polling&t=1402016180378-0

Which are all 404. So I guess this is part of the new protocol that is not compatible. I don't know whether 1.0.x intends to be incompatible with the old protocol, or whether it is failing the to the CORS error (which makes it impossible for it to see that it is a 404).
Comment 1 Ori Livneh 2014-06-06 02:57:22 UTC 
v1.0 changes the protocol substantially. Apart from bragging rights about using the latest and greatest, I don't see major gains to be had. 0.9 is well-tested. IMO, we should upgrade in lock-step with what is available in Debian Testing.
Comment 2 Ori Livneh 2014-06-06 02:58:10 UTC 
(Not to mention: we want to give the popular client libraries time to upgrade, too.)
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links