GObjectification of protocols

John Bailey rekkanoryo at rekkanoryo.org
Mon Aug 19 18:43:44 EDT 2013

On 08/19/2013 12:54 PM, Tomasz Wasilczyk wrote:
> 18 sie 2013 21:53, "Ankit Vani" <a at nevitus.org <mailto:a at nevitus.org>> napisał(a):
>> This makes using smaller interfaces for convinience not necessary, but it may
>> still be appealing if we want PurpleProtocolInterface to not be so huge.
> I like the idea of small interfaces. But you should pick carefully, which
> methods should stay in main class.

In general I agree with the several smaller interfaces idea.  This could be an
interesting debate, though.  For example, an argument could be made to have the
file transfer related bits split off as a smaller interface, since not all
protocols support file transfer (Facebook XMPP, for example).  Note that I'm not
making this suggestion, just pointing out a possibility.

> Also, I think there should still be some padding bytes, in case of any
> unexpected upgrades, that should stay in the main class.

I agree entirely.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: OpenPGP digital signature
URL: <http://pidgin.im/pipermail/devel/attachments/20130819/f5477917/attachment.sig>

More information about the Devel mailing list