So, ages and ages ago, for WebSockets support, the idea of an upgradeHead was added. This is for the data that directly trails the headers in a Upgrade or Connect request. Whilst the spec doesn't really say what this is, I propose making this as the first data event, rather than as a extra argument to the upgrade or connect events.
This seems like the better way to do this, although, I know it'd be a huge change in API from what we currently have, which is fairly popularly used at present.
I feel that we should've really implemented it this way round in the first place, but there were a whole bunch of reasons as to why this proved difficult at the time.
Thoughts?
So, ages and ages ago, for WebSockets support, the idea of an upgradeHead was added. This is for the data that directly trails the headers in a Upgrade or Connect request. Whilst the spec doesn't really say what this is, I propose making this as the first data event, rather than as a extra argument to the
upgradeorconnectevents.This seems like the better way to do this, although, I know it'd be a huge change in API from what we currently have, which is fairly popularly used at present.
I feel that we should've really implemented it this way round in the first place, but there were a whole bunch of reasons as to why this proved difficult at the time.
Thoughts?