Hello, I am a 20 year veteran of perl coding, but have taken that long to get around to a project that I think is worth sharing with the rest of the community. I am taking part in the IETF httpbis working group and creating an implementation of the HTTP-draft-04/2.0 specification. The initial goal of this implementation is to participate in the IEFT httpbis interim interop session in Hamburg at the beginning of August. Eventually I would like it to evolve into a standard HTTP/2.0 implementation for use by all. Walk, crawl, run.
My inclination is to create modules in a new Net:HTTP2 namespace. For example: Net::HTTP2 Net::HTTP2::Compress Net::HTTP2::Frame Net::HTTP2::Stream Net::HTTP2::Connection Asynchronous IO code will leverage IO::Async ( IO::Async::SSL ): IO::Async::HTTP2::Framer Client and Server libraries which leverage the above protocol level libraries will be in: Net::HTTP2::Client Net::HTTP2::Server There will also be example scripts using the above two libraries which may or may not be appropriate for inclusion. I am considering making a user-agent interface compatible with LWP::UaerAgent. Long term my hope would be LWP would leverage the above code, or something like it, for its HTTP/2.0 capability and few would use the HTTP/2.0 code directly. What are your thoughts? I am not married to any naming scheme. The above seemed logical. As an aside, in development of the HTTP2 I bootstrapped with a (yet another) SPDY/3 implementation. I am very happy to contribute that as well but my gut says it would make more sense to build on one of the two existing modules I found rather than adding a third. -stephen
