Hrm, "not really" except that I may end up needing to support a couple of 3rd party plugins here and there. =D It does mean there's a good chance I won't have to keep running along behind them when they make changes. The more things that they do like this, the less likely it is that they're going to keep messing with the protocol. This makes me happy. ;D Anyway, my read of that is that they are providing toolkits to write a 3rd party aim client yourself, but not having to "make up the protocol" so to speak. Likewise, they've provided a way to plug in 3rd party functionality. Anyway, I think it's definitely a neat addition! Clearly they need to open source the entire thing. ;D ;D ;D (is the SDK itself open source, btw? just glancing over, I get the impression you'd get a "closed source SDK" but then you can all sorts of neat stuff with it)
Daniel On Mar 6, 2006, at 9:11 AM, Aaron Axelsen wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Does this mean anything for pyaim development? > > http://developer.aim.com/ > > - -- > Aaron Axelsen > [EMAIL PROTECTED] > > Great hosting, low prices. Modevia Web Services LLC -- > http://www.modevia.com > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.2 (MingW32) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFEDEMWuucONIvD0AMRAvZRAJ92WpUvTG1pT4hNFVBS1FYyt/fgkwCcD7gT > 1Y4bB1N0jMlA1wJs8Fmu28s= > =vaY4 > -----END PGP SIGNATURE----- > > _______________________________________________ > py-transports mailing list > [email protected] > http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports > >
