Re: Re: What lowlevel protocols are natively available in PHP?

Hey, On Fri, Aug 21, 2009 at 10:01 PM, chris.<peardev@dnswatch.com> wrote: > > On Thu, August 20, 2009 6:19 pm, till wrote: >> On Thu, Aug 20, 2009 at 11:09 PM, chris.<peardev@dnswatch.com> wrote: >> >>> >>> On Thu, August 20, 2009 6:52 am, Greg Beaver wrote: >>> >>>> chris. wrote: >>>>> Greetings, >>>>> I've applied for maintainer of the currently unmaintained >>>>> Net_Traceroute pear package. If I'm given the opportunity to >>>>> be it's maintainer, I'd like to add/enable the full range of UDP, >>>>> TCP, >>>>> GRE, and ICMP that TRACEROUTE(8) provides. I've >>>>> just completed a PHP traceroute utility that does just that- it can >>>>> manipulate (utilize) every option that TRACEROUTE(8) provides. But >>>>> I >>>>> must use the protocols native to my system (UNIX/BSD) in order to >>>>> use it. As NET_Traceroute currently stands - it's broken. PHP(5) >>>>> complains that it doesn't make it's calls in a manner compatible >>>>> with (current) versions of PHP. Anyway, if given the role of >>>>> maintainer of the package, I'd _really_ like to "jump start" it. >>>>> But >>>>> before (possibly) re-inventing the wheel. I felt I should find out >>>>> how much PHP already provides in the way of UDP, TCP, GRE, and ICMP. >>>>> >>>>> >>>>> Thank you for all your time and consideration. >>>>> >>>>> >>>> >>>> http://php.net/fsockopen >>>> http://php.net/socket_create >>>> >>>> >>>> >>>> sockets support in php is pretty abysmal >>>> >>>> Greg >>>> >>>> >>>> >>> Hello Greg, and thank you for your reply. >>> Yes, I had already read those when initially attempting to determine >>> what might already be available. If that's all there is, it appears that >>> I'll have a lot to do. :( >>> >>> >>> Thanks again for your reply. >>> >>> >>> --Chris >>> >>> >> >> Hey Chris, >> >> >> I hope this is no set back. :-) >> >> >> I'm not sure if this has been shared, but generally, if you want to >> maintain/takeover a package, please provide some patches on the bug tracker >> first so "we" get an idea of who you are and what you are capable of (no >> offense meant :-)). >> >> So in case of Net_Traceroute please provide some patches for the >> features you plan (make sure to follow the CS along with other things) and >> open tickets on the bug tracker. One of the advantages I (personally) see >> is that the package is very young (alpha) which allows you to do virtually >> whatever you want (BC breaks, converting to PHP5, exceptions, whatever is >> needed). >> >> A great example of how this process works is the recent progress on >> Spreadsheet_Excel_Writer (see mailing list archives). >> >> >> Let me know if you have questions, >> Till > > Greetings Till, and thank you for the thoughtful (and insightful) reply. > I read http://pear.php.net/manual/en/newmaint.takingover.php, > and > followed this: > 1) > The first thing is to inform the PEAR Quality Assurance mailing list about > your intention. If you have not been involved in PEAR prior to that, it is > a good idea to write a few words about you and your motivations. > > it then indicated: > 2) > The QA team will then state whether you can take over the package or not, > eventually explaining why. You can then apply for an account for the PEAR > website unless you already have one. The PEAR Group will have to grant > this account, and afterwards the QA team will assign you as the new lead > maintainer for the package. > > I also read http://pear.php.net/manual/en/guide-developers.php > > I was unable to discover the "send patch sets against the buglist" > in any of the "prerequisites". But point(s) well taken, thank you. > > > Best wishes. > > --Chris > I didn't mean to discourage or belittle your efforts. I hope I didn't come across like that. :-) I think everyone agrees that all contributions would be welcome. I just stated the "how it usually works". Cheers, Till