mojolicious/mojo

HTTP/2 and HTTP/3

Open

#423 opened on Dec 2, 2012

View on GitHub
 (45 comments) (4 reactions) (0 assignees)Perl (591 forks)auto 404
feature requesthelp wanted

Repository metrics

Stars
 (2,745 stars)
PR merge metrics
 (PR metrics pending)

Description

The final HTTP/2 spec is still at least 1-2 years away, but now that the first draft (based on SPDY) has been released, i believe we can at least start planning our implementation.

http://tools.ietf.org/html/draft-ietf-httpbis-http2-00

While details like the upgrade mechanism from HTTP/1.1 and mandatory TLS encryption are very likely to change, major features like multiplexing are pretty much a given, and will require some refactoring in Mojolicious.

Contributor guide

Research direction
Study the existing HTTP/1.1 implementation in Mojolicious, understand SPDY if present, and research HTTP/2 and HTTP/3 specs. Then propose a refactoring plan.
Tech stack
perl
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Needs investigation
Prerequisites
PerlHTTP
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20