Skip to content

Details

Details

//=================

Oh dang, it's February and you know what that means?! Another month of party with SeattleJS!

//=================

Topic 1: HTTP/2 in Node.js? Sure, We can do that!
by James Snell
Github (https://github.com/jasnell)| @jasnell (https://twitter.com/jasnell)

abstract:: Support for the HTTP/2 protocol has been added to Node.js. This talk will give a walk through of how it works, how to use it, and how to take advantage of the new features the protocol enables.

bio:: James is a core contributor to Node.js core and the primary author of the HTTP/2 implementation.

//=================

Topic 2: Demystifying HTTP Status codes
by Michael Krotscheck
Github (https://github.com/krotscheck)| @krotscheck (https://twitter.com/krotscheck)| Website (https://krotscheck.net/)

abstract:: You've successfully built an XMLHttpRequest or fetch client, but now your api is returning weird numbers. What do they all mean?! This lighning talk will cover all of the weird -- but useful! -- http status codes that you're likely to encounter during everyday API usage. The talk will answer questions like:

Success doesn't always mean the same thing: 200, 201, 202, 204
Redirecting with 300, 301, 302, 307 and 308
Caching status codes (304)
What is the difference between 401 and 403?
What's in a 404?
Conflict resolution (409)
Why twitter is full of stoners (status code 420, 429).
The importance of coffee (418)

Related topics

You may also like