Getting rid of bad design

Posted Jun 5, 2014 10:42 UTC (Thu) by Wol (subscriber, #4433)
Parent article: Should the IETF ship or skip HTTP 2.0?

Reading tfa, I think there is a good reason for shipping it.

But before you do

1) Add the requirement that an http/2 compliant browser/server may not *initiate* the use of deprecated features, and

2) All those naff features? Deprecate them!

Not quite sure how you get round deprecated features with no alternative, maybe mark them for future deprecation, and introduce 2.1, 2.2 etc as replacements get invented.

But that way, you can easily start designing http/3, knowing that all those features will be disappearing.

Cheers,
Wol