> But I get your point.  The idea of being able to load the plugins "as-is" is 
> exactly what I would try to achieve.  That way, all the effort goes into 
> building the transport once... 

I personally like the approach PyMSN-t is taking: write a modular
transport (adaptable to other protocols) in Python, use the protocol
implementation of Twisted for the protocol specific things. I personally
have more trust in Python implementations than in the Gaim C libraries.
They're probably a bit more (easier) portable too.

That's why it would be cool if protocol-specific effort went into
Twisted, and that other transports also base themselves on the PyMSN-t
framework for building transports.

cheers,
Remko
_______________________________________________
jdev mailing list
[EMAIL PROTECTED]
https://jabberstudio.org/mailman/listinfo/jdev

Reply via email to