RE: [PEAR-DEV] possible (real) Net_ICQ/AIM/OSCAR pear package (?)

> I would preffer to separate the packages. The goals for an unified > Net_IM are too big. IMHO each protocol should have its own package, > developers, release cycle, doc, etc, and if there is people willing to > create the abstraction package Net_IM, it would be another package too I fully agree with this. My code is there to provide communication with the ICQ network and I don't think that it would be a good idea to create a Net_IM package since there is no other protocol implementation out there yet (and maybe will never be). In addition protocols each have a unique structure so it would be very confusing to read the code since there are different developers for each (...) etc. I don't see any reason to do some work on a multiple protocol implementation in Net_IM because there are no other protocols supported than the one I am talking about. I even don't have a clue about creating Net_IM as abstraction layer - since you have to decide which protocol you are going to use it is a good idea to sepperate the packages. "Net_ICQ" seems to be the best matching name because the class is intended to communicate with ICQ. Net_Oscar would mean that there is support for AIM too but in fact it is very limited to basic features and not intended. regards