maximum protocol message size from libpurple (for OTR plugin)

[Moritz Warning]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 01/05/2014 05:04 AM, Mark Doliner wrote:
> On Mon, Dec 23, 2013 at 9:14 AM, Moritz Warning <moritzwarning at web.de> wrote:
>> My question is when we can expect to have a way to expose the protocols
>> maximum message size? Someone on IRC kindly told me that I have to
>> wait for libpurple 3.0. Is there a time frame?
> 
> Our current main branch of development does contain a prpl function
> 'get_max_message_size'. It's not defined for all protocol plugins, and
> where it IS defined, it's not necessarily correct. In fact, most of
> the values we're using were taken from the OTR plugin. The nature of
> using undocumented proprietary protocols is such that it's not easy to
> know the maximum message size. It's usually determined through trial
> and error.
> 
> There is no ETA for libpurple 3.0
> 

Thank you for the concise answer. :)

The values taken from OTR plugin seem to work for OTR,
so that is fine for me. :>

I will try to make the configuration entries for the OTR plugin
from within the protocol plugin. This is dirty, but might work
fine for the time being.

- - mwarning
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Icedove - http://www.enigmail.net/

iQEcBAEBAgAGBQJSyVsOAAoJECHrh56PP4wphh0H/0+j15gNLIg2meF8KsKjniaB
iwJHMb9cKp90G4SpCwULnF4Vuy+r42yGkSEx75aBCE4oEVoRkAgeJlETEaZnIqgx
Qgap8pHlO13pz4rcpXGRBFopeyDaQHZe6UNQAZL4Q0g5ZtLyWHQWZQPx4QdgjTui
0j3EK/FCA2FeEsEjrSPcrxRDOh3/6Z/ChV9xr/e0uWcFQL2CQSeafEi2MNKl0w0R
VnkwOw7Y+slJzjsgmxoRieEOhXc/BwXOsq1ufTjl9UqHDWsPXNXOrDpLmTnrIIDF
SCADBgmctVd4rBfhwhpzMRkRb+M5MzNhTEf97/b2804XXOX+VcecMUi8FvyX7Cs=
=Na3U
-----END PGP SIGNATURE-----