Summary: | [Qt] Change default WebSocket protocol to the latest one | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Yuta Kitamura <yutak> | ||||
Component: | WebKit Qt | Assignee: | Yuta Kitamura <yutak> | ||||
Status: | RESOLVED FIXED | ||||||
Severity: | Normal | CC: | ahf, cmarcelo, hausmann, jesus, jturcotte, kenneth, laszlo.gombos, ossy, webkit.review.bot | ||||
Priority: | P3 | Keywords: | Qt | ||||
Version: | 528+ (Nightly build) | ||||||
Hardware: | All | ||||||
OS: | All | ||||||
Attachments: |
|
Description
Yuta Kitamura
2011-12-01 23:44:41 PST
Sure, we would be happy with that change :) I'd say go for it. I'm not aware of anyone using the Qt port and relying on a particular web socket protocol version. I'm inclined to say that our interest is to follow the majority of the other ports in this regards and if there was a "project default" (that ports _may_ optionally deviate from), then I think we'd be in the group interested in following the default, at this point. We never officially supported the InspectorServerQt in WebKit/qt but this will break the support for QtWebKit clients with it. On the other hand I need this to be switched on to support the new remote inspector in WebKit2, so I'm looking forward to this :) (In reply to comment #2) > I'd say go for it. I'm not aware of anyone using the Qt port and relying on a particular web socket protocol version. I'm inclined to say that our interest is to follow the majority of the other ports in this regards and if there was a "project default" (that ports _may_ optionally deviate from), then I think we'd be in the group interested in following the default, at this point. I'm fine with either following the project default or switching right now. Before switching the project default, I'd like to confirm the hybi tests run fine on WebKit2 bots (and fix any issues if found). The tests aren't run at this moment as WebKitTestRunner lacks LayoutTestController.overridePreference() implementation. What is the status of this? GTK already transitioned (bug 74064), Mac/Win/WK2 also transitioned (bug 78541). So I think, among the ports I'm aware of, Qt is the only one left on the old protocol. Sounds like it's time to switch the flag for Qt, and also flip the WebCore-global default value. I'd like to make the transition two-fold: 1) Complete the transition on Qt and make sure things are fine. 2) Flip the global default value and remove port-specific defaults. Does this make sense? If so, I'm going to upload a patch that just changes Qt's default. (In reply to comment #6) > I'd like to make the transition two-fold: > 1) Complete the transition on Qt and make sure things are fine. 1.9) Announce webkit-dev about the transition. > 2) Flip the global default value and remove port-specific defaults. (In reply to comment #6) > Does this make sense? If so, I'm going to upload a patch that just changes Qt's default. I'm fine with it and according to previous comments here I believe the others also are. Created attachment 131887 [details]
Patch
Comment on attachment 131887 [details]
Patch
rs=me
Comment on attachment 131887 [details]
Patch
Thanks!
Comment on attachment 131887 [details] Patch Clearing flags on attachment: 131887 Committed r110905: <http://trac.webkit.org/changeset/110905> All reviewed patches have been landed. Closing bug. |