Net_ICQ...and pear talks OSCAR
| From: | daniel @ swn | Date: | Thu, 28 Aug 2003 05:51:07 +0000 |
| Subject: | Net_ICQ...and pear talks OSCAR | ||
| Groups: | php.pear.dev | ||
| Request: | Send a blank email to pear-dev+get-20710@lists.php.net to get a copy of this message | ||
It's me again,
I nearly finished converting my code to "Net_ICQ" in pear package
format. There has been a discussion about a Net_IM pear package that
would cover other IM protocols in the future, too, and I am not sure
about that point. Since there are no other protocols supported yet it
would be a good idea to make the package working without a Net_IM parent
package for now. Net_IM makes sense in the future. Such a parent package
would need additional code (Net_ICQ's code is very complex already) and
in my opinion every protocol should have its own package Net_IM could
use as a dependency. However, most developers will use one protocol only
and do not need an additional parent package..mh..In addition I do not
know any other protocols than Oscar (yet) so I am not the right person
to develop a parent package for all of them (:
I decided to keep basic AIM support in Net_ICQ for possible later use.
Currently I do not know if it's possible to extent it because AIM uses
direct connections for most features and got a clone detection I cannot
work around cause it reads from aim.exe's memory. It currently supports
online and offline notices, contact list, maybe visible and invisible
list and simple type 1 messages for AIM. ICQ features are the same and
advanced type 2 messages (message, added, auth, greeting card,
contacts), pager, auto messages, register new uin and search for users.
Currently my directory structure looks like this:
Net_ICQ-0.1/ICQ.php - class Net_ICQ
Net_ICQ-0.1/ICQ/defines.php - constants with prefix "ICQ_"
(ICQ_MTYPE_PLAIN for example)
Net_ICQ-0.1/ICQ/functions.php - class Net_ICQ_func, some basic functions
Net_ICQ-0.1/ICQ/outgoing.php - class Net_ICQ_out, outgoing packet
creation
Net_ICQ-0.1/ICQ/incoming.php - class Net_ICQ_in, incoming packet parsing
Net_ICQ-0.1/ICQ/examples/example.php - a simple ICQ bot using every
feature (works for AIM, too)
Net_ICQ-0.1/ICQ/examples/register.php - example on uin registration
Net_ICQ-0.1/package.xml
Is anything wrong with this or is it acceptable?! =)
Hope to be able to make my sources available in a few days so that you
can take a look at it and tell me what still needs to be done (:
regards,
Daniel