Re: the dilemma of 3 different Pear IRC classes.. solved?
| From: | Mirco "MEEBEY" Bauer | Date: | Sat, 04 Jan 2003 09:35:27 +0000 |
| Subject: | Re: the dilemma of 3 different Pear IRC classes.. solved? | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-12083@lists.php.net to get a copy of this message | ||
I don't understand any of this as a flame :) no way...
its showing your goals of Net_IRC, which is great (this is exactly what I requested on #pear IRC
channel)
I think we should add our goals to the package descriptions, because users can choose then what kind
of IRC
class they need, and btw its also an advantage to have all IRC classes available at one point
(PEAR), they
see right away they are different ones, and the difference with the goals are explained...
I think this problem of 3 IRC classes _is_ solved, well done guys!
On Fri, 3 Jan 2003 20:15:04 -0800
"chip" <chip@force-elite.com> wrote:
> This isn't supposed to be a flame at SmartIRC or Yapircl.
>
> I said what I believed to be facts at this time, if I am incorrect about
> anything I said, please tell me -- it was not intended.
>
> I hope this mail will also better explain to the wider Pear community why
> there are 3 different IRC classes at this time.
>
> All three of us authors got a chance to talk on IRC today.
>
> I have decided on what Net_IRC's Target / Niche will be:
>
> 1) Run on standard PHP 4.3+
> (no extra extensions - right out of the zip file/make install)
> Currently Yapircl and SmartIRC require a non-standard, experimental,
> extension to run.(they use socket_*). SmartIRC has the ability to use
> fsockopen, but it is by no means good at it(using a looping usleep around it
> -- note: this the absolutely worst way todo it in Windows, since it doesn't
> have usleep, it will be a nice tight read loop, eating up CPU).
>
> 2) Run on all PHP Platforms (FreeBSD, Linux, Windows, etc)
> I don't believe either of the other authors has really made this a large
> priority. I would like Net_IRC to run completely cross platform, and do it
> well. (Windows being the kicker)
>
> 3) Native multiple server connections
> Both SmartIRC and Yapircl do not support multiple server connections natively
> at this time. meebey(SmartIRC author) has said he doesn't support the concept,
> and if you want an irc client/bot on more than one server, you should run two
> sperate PHP process. Yapircl does support more than one server at a time but
> this is done by creating more than one object at a time. There is an example
> of this included with Yapircl. However, this solution is more a "hack on" way
> todo it. I have tested Net_IRC on my internal IRC server with more than 300
> concurrent connections. While the vast majority of users will never need
> that, I think the ability to connected to multiple servers, wether it be 2, 3,
> 10, or 400, is a good feature, and to support it natively without requiring a
> "hack on" method is a unique feature that is needed.
>
>
> Since both Net_IRC and Yapircl are both under the PHP License, I have talked
> to gtk(Yapircl author), and I think we will both benifit from some code
> sharing. To my knowledge SmartIRC will only be LGPL, which is rather useless
> for me and gtk, as we can't use any code from it directly.(and defining if
> include() violates the LGPL.. well ill let somone else do that.)
>
> -chip
>
> --
> PEAR Development Mailing List (http://pear.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php
>
Mirco Bauer aka MEEBEY
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GIT d s-: a--- C++ UL++>++++ P L++$>+++$ E W+++$ N o? K- w++>! O- M- V? PS
PE+ Y- PGP>++ t 5+ X++ R tv+ b+ DI? D+ G>++ e h! r>++ y?
------END GEEK CODE BLOCK------