- **status**: unassigned --> invalid
- **Milestone**: 5.0.2 --> never
---
** [tickets:#2285] LOG: Check size of logBufSize could be non backward
compatible**
**Status:** invalid
**Milestone:** never
**Created:** Thu Feb 02, 2017 01:44 AM UTC by Minh Hon Chau
**Last Updated:** Thu Feb 02, 2017
Hi Vu,
"Consistent" in AIS spec seems not clear, some can inteprete to count length
with null pointer, some may not. This issue had been flagged in review of
#2038. After this check is introduced, applications may still be running
without problem, some may receive INVALID_PARAM. I guess it's po
Hi Minh,
I think, the applications encountered this case have to fix the wrong code from
their side as they have not followed the NTF AIS spec correctly.
Here is the statement from the AIS spec.
> additionalText optional – length must be consistent with lengthAdditionalText
Also, I remember the
---
** [tickets:#2285] LOG: Check size of logBufSize could be non backward
compatible**
**Status:** unassigned
**Milestone:** 5.0.2
**Created:** Thu Feb 02, 2017 01:44 AM UTC by Minh Hon Chau
**Last Updated:** Thu Feb 02, 2017 01:44 AM UTC
**Owner:** nobody
NTF has received INVALID_PARAM wh
