3 ms·
I don’t understand. How can Google just arbitrarily decide to not support part of a standard because it’s easier for them?
by Aeolun 6y ago
I don’t understand. How can Google just arbitrarily decide to not support part of a standard because it’s easier for them?
- jabiko 6y agoIt is optional for a client to support server push. It I understand the RFC correctly a client can announce server push support via the SETTINGS_ENABLE_PUSH setting. So if a client chooses not to announce push support it is still standard compliant.
- martin_a 6y agoTwo words: Market domination.
- nolok 6y agoPlease, they're the one that added this in SPDY to begin with. They would do that even if they were a minority player because the reason they actually remove it is that it provides no gain for the work required.
- martin_a 6y agoWell, either it's a standard or not. And if the most powerful browser vendor decides to drop support for standardized features that is a strong "political" signal against the standard and it absolutely has a different meaning...
- nolok 6y agoI don't understand. What makes you think Google or any other company out there HAS to support the entirety of a (non certification dependant) standard if they estimate that they could drop a part of it at no loss / at a gain ? Is your company properly supporting HEAD on its website ? Probably not (treat it as GET), because it's easier and no real loss is incurred. Same here.
- kaetemi 6y agoAlmost as if there's no standard, and everything's really just running on a proprietary Google protocol...