Extracted from IRC: ...etc... 11:51 <@alexis> rogerroger: Implemented websocket support on the server. https://github.com/mozilla-services/loop-server 12:41 < jbonacci> alexis how does the implementation of websocket support change/impact the load test? 12:42 < jbonacci> any additions/changes required? 02:28 <@alexis> jbonacci: yes changes are needed there. 02:29 <@alexis> jbonacci: need to update the loadtest to test the websocket protocol 02:29 <@alexis> jbonacci: that's another big part, gasp. 08:21 < jbonacci> alexis ok, I will probably open an issue for that Looking around, I see the following related tickets and issues: bug 1025872 https://github.com/mozilla-services/loop-server/pull/115 https://github.com/mozilla-services/loop-server/pull/126 There is probably a bit more than this, including
that last line should have said There is probably a bit more than this, including API and/or doc changes. Leaving this for :alexis to fill in the blanks.
Possibly useful: https://github.com/mozilla-services/loads/pull/73
Assignee: nobody → tarek
Severity: normal → major
Priority: -- → P2
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
Yea, can now see this in the 'make test' results: Bytes received via web sockets : 454 and verified the loadtest.py file.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.