Problems with file transfer API

[Tomasz Wasilczyk]

W dniu 17.02.2014 17:38, Ankit Vani pisze:
> In the gobj.plugins branch, a protocol can implement the
> PurpleProtocolFactoryIface and implement the xfer_new function of it to return
> an object of a protocol-specific subclass of PurpleXfer (called if defined, by
> purple_xfer_new).
>
> The appropriate file transfer functions can be made virtual and added to
> PurpleXferClass. The protocol-specific subclasses can override whatever virtual
> functions they need to.

I mean exactly this. But this is only the first step. The base class is 
still huge and complicated, just like it was in 2.x.y. To make it clear, 
the protocol-specific subclasses could be derived also from the 
subclasses I mentioned:

PurpleXferClass <- PurpleFDXferClass <- YahooXferClass (an example).

Tomek

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4225 bytes
Desc: Kryptograficzna sygnatura S/MIME
URL: <https://pidgin.im/pipermail/devel/attachments/20140217/79aebb07/attachment.bin>