When a large number of Diameter messages are being exchanged between the client and the server, the incoming stream might be divided into multiple batches, where each batch does not necessarily consist of an integral number of messages. The following 5-message scenario explains the issue.
5 messages are being sent in two batches:
Batch 1:
-----Message1---------|-------Message2---------|------------Message3-------------|--------Message 4 part1
Batch 2
-----Message 4 part 2------|------------------Message5-------|
The current implementation does not take into account this case; it considers data streams as independent of each other.
When a large number of Diameter messages are being exchanged between the client and the server, the incoming stream might be divided into multiple batches, where each batch does not necessarily consist of an integral number of messages. The following 5-message scenario explains the issue.
5 messages are being sent in two batches:
Batch 1:
-----Message1---------|-------Message2---------|------------Message3-------------|--------Message 4 part1Batch 2
-----Message 4 part 2------|------------------Message5-------|The current implementation does not take into account this case; it considers data streams as independent of each other.