Next HTTP WG Meeting

[jasnell]

@nodejs/http ... It looks like I completely overlooked the previously scheduled HTTP WG call. Given the holidays, I'd suggest that we skip further HTTP WG calls this month and schedule the next meeting in January. I'll set up the agenda when we get closer.

[hueniverse]

I'm out till mid January.

[bradisbell]

Is this project still active? Is there a future meeting planned?

[jasnell]

The WG is more or less a review team for any PRs related to the http
module. If/when the need for something more substantial than that arises we
can get meetings rolling again. Have something in mind?
On May 22, 2016 5:47 PM, "Brad Isbell" [email protected] wrote:

Is this project still active? Is there a future meeting planned?

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#14 (comment)

[bradisbell]

Have something in mind?

Nothing that hasn't been already proposed. I've just found myself monkey patching internals of the HTTP parser for a new Node.js version again, remembered this group, and wondered if anything was new. (I do this about every year, since parser.execute isn't a published API and is always subject to change. Each time it changes, I need to find a new method of patching in custom methods and working around not-quite-RFC-compliant clients.)

Hopefully some day I'll get around to learning the Node.js internals and will be able to meaningfully contribute.

[jasnell]

Understood.
On May 22, 2016 5:59 PM, "Brad Isbell" [email protected] wrote:

Have something in mind?

Nothing that hasn't been already proposed. I've just found myself monkey
patching internals of the HTTP parser for a new Node.js version again,
remembered this group, and wondered if anything was new. (I do this about
every year, since parser.execute isn't a published API and is always
subject to change. Each time it changes, I need to find a new method of
patching in custom methods and working around not-quite-RFC-compliant
clients.)

Hopefully some day I'll get around to learning the Node.js internals and
will be able to meaningfully contribute.

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#14 (comment)