[jdev] Re: New MSN-t in the works

[Peter Saint-Andre]

In article <200408111136.53098.james at delx.cjb.net>,
 James Bunton <james at delx.cjb.net> wrote:

> > Contact me directly ... I had the same problem when porting Yahoo to
> > JCR. I replaced the 'mtq' functions with glib-2.0 equivalents to get the
> > same functionality, if you are interested.
> Yeah, it might be useful to have a JCR version as well as the Python one.
> Could you let me know how you did it? I don't have any experience with glib.
> 
> > On another note ... I'm looking into using Gaim plugins as the
> > "transport layer" and building a generic transport framework. The Gaim
> > plugin API has most of the functions we would need for a transport, and
> > this may be a way to streamline the development of transports for Jabber.
> >
> > Of course, I'm very interested in MSN-t with Twisted. Perhaps that would
> > be a way to make a set of the legacy transports ... AIM, MSN, and Yahoo.
> > Anything that will make the transport more usable and esaier to maintain.
> I think twisted would be a lot easier to work with than the GAIM plugins. 
> It's 
> a framework for creating networked applications that may use multiple 
> protocols. http://www.twistedmatrix.com for more info.

Would it be possible to somehow build the GAIM plugins into Twisted? I 
know that Twisted has support for lots of protocols, but the closed IM 
protocols are not on that list AFAIK.

/psa