Re: [liblo] maximum size of message

Hi Steve
one thing that's odd is when liblo has different (compile-time) max sizes
set on different hosts making them partially incompatible. Can we make a
difference of UDP and TPC max sizes and maybe put the TCP max to a larger
value per default (without touching the API) as a non-intrusive step
towards larger possible TPC messages. Are there any overseen obstacles,
what do you think?
Tom

On Tue, August 19, 2014 15:25, Stephen Sinclair wrote:
> Hm, well I can't think of an easy way to do that with the current API.
> It could be something to consider for a future version of liblo.
> Currently the maximum message size is a global compile-time variable.
> It could potentially be changed to a run-time global, but some of the
> buffering code would definitely need to be changed so as to avoid large
> stack allocations.  Additionally there is the security consideration that
> an attacker could cause problems by sending a never-ending message stream.
>
>
> Steve
>
>
> On Thu, Aug 14, 2014 at 5:34 PM,  <to...@tr...> wrote:
> >> On Wed, August 13, 2014 23:57, Stephen Sinclair wrote:
>>>>
>>>> I wondered if it would be possible to not limit the size of TCP
>>>> messages so it would be possible to send large messages.
>>>>
>>>
>>> It does make sense.  I'm surprised there's ever a need for OSC
>>> messages greater than 32k, what are you sending?  in any case, in
>>> principle there should be no real limit for TCP.  The limit just
>>> simplifies much of the programming, and I'd have to check over the
>>> code again to be sure it doesn't cause any ill effects to increase the
>>> limit.  Increasing this variable likely causes liblo to allocate much
>>> larger buffers, so I'm not sure that's an appropriate fix, even if it
>>> works.
>>>
>>> Steve
>>>