Re: [PEPr] +1 for Web Services::Services_oEmbed

Hi, David Jean Louis wrote:

Is this needed? As I'm a lead developer of HTTP_Request, I can register HTTP_Request2 on PEAR website. And also move current feature requests to it, hehe.

Well, registering the package (and before this, making a pepr) is one thing (the last step imho), setting up a temporary repo to enable people to start collaborate is another, no ?

There is no need to go through PEPr for a new major version. Also what prevents us from using PEAR infrastructure for collaborating?

First priority IMO is HTTP_Request2_URI class which will conform to RFC 2396 and use "official" regexps and algorithms from there. Original author of Net_URL(2) and HTTP_Request, unfortunately, isn't a very keen RFC reader. Then porting current HTTP_Request and adding cURL support.

I won't go in this kind of debates. Seems just flames to me.

That's not flame, but a result of fixing bugs in HTTP_Request for several years.

But imho making a HTTP_Request2_URI is just duplicating Net_URL2 package, if there are bugs in this package they should be fixed instead of making another package.

There are no "bugs" in there, but bad architectural decisions. I'd rather create my own correct implementation from scratch than deal with yet another package and its BC horror, thank you very much. I also don't care about "duplicating" anything, besides the scope of HTTP_Request2_URI should be a lot narrower than that of Net_URL2.