From fd6ce1632588efca1ddb8815b3cac16ce076effa Mon Sep 17 00:00:00 2001 From: Lilleman auf Larv Date: Fri, 25 Sep 2026 19:04:28 +0200 Subject: [PATCH] Drop a false multiple from the changelog, and name the new per-segment charge --- CHANGELOG.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index f5857a8..822a669 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -35,9 +35,10 @@ - An `alert_notification` or an `outbind` from the peer is logged and left unanswered, as SMPP 3.4 gives neither a response. Each one used to emit `sessionError`, `"alert_notification" has no response command`. -- `maxOctets` charges each held segment, and every TLV it carries, for the memory it keeps beyond - its octets. A peer could hold around 67 times the cap with segments of empty fields, and megabytes - per segment with thousands of empty TLVs, both of which the cap counted as next to nothing. +- `maxOctets` charges each held segment about 1 KB, and every TLV it carries 300 octets, for the + memory they keep beyond their octets. Segments of empty fields or thousands of empty TLVs used to + count as next to nothing, so a peer could hold far more than the cap. A `maxOctets` tuned low now + holds fewer segments. - `server()` refuses a `maxOctets` below 1 or not a whole number, `Infinity` included, like its other limits. `server({ maxOctets: 0 })` used to start and then refuse every multipart message. - `callback_num`, `callback_num_atag`, `callback_num_pres_ind`, `broadcast_area_identifier` and