Re: Naming for HTTP/2.0 modules

2013-07-14 Thread Stephen Ludin
That is workable. I will go with a new top level namespace if that is what folks think is best. I went with Net:: because the page that discussed naming: https://pause.perl.org/pause/authenquery?ACTION=pause_namingmodules Explicitly lists HTTP as one of the protocols it was originally designed

Re: Naming for HTTP/2.0 modules

2013-07-14 Thread brian d foy
[[ This message was both posted and mailed: see the "To," "Cc," and "Newsgroups" headers for details. ]] In article <51e1f571.6090...@savage.net.au>, Ron Savage wrote: > HTTP2::* is good, but after that perhaps an indicator of the draft > status, to give HTTP2::Draft::*. This can be removed

Naming for HTTP/2.0 modules

2013-07-13 Thread Ron Savage
Hi Steve I don't see the need to put Net::* on the front of your namespace. Does it actually add anything? See the last link for details on 'Net'. HTTP2::* is good, but after that perhaps an indicator of the draft status, to give HTTP2::Draft::*. This can be removed or changed later. That w

Naming for HTTP/2.0 modules

2013-07-12 Thread Stephen Ludin
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 go