Interest check: segmented writes support (WriteProperty / WritePropertyMultiple)

[EveGun]

Hi! We’re using @bacnet-js/client and are hitting payload-size limits when writing larger values (especially schedules/calendars and larger WritePropertyMultiple payloads).

From what we can see, the client currently handles segmented responses, but not segmented confirmed requests (segmented writes).

We’ve reviewed the code and this looks like a relatively large feature (TX segmentation state machine, SegmentAck/window handling, retries/timeouts, and test coverage).
Before investing in this, we’d like to check community/maintainer interest.

Would others be interested in native support for:

segmented WriteProperty
segmented WritePropertyMultiple
SegmentAck handling (window/retry/timeout)
Also: do maintainers expect this to require any breaking API/behavior changes, or should this be implemented fully backward-compatible?

If this is relevant for you, please share your device/use-case and whether this is blocking production usage.
We’re open to contributing if there is interest.

[robertsLando]

Hi @EveGun and thanks for your interest in our repo!

Yes we are interested in this! just be sure to keep no breaking changes (or as low as possible) and add coverage tests 🙏🏼

[EveGun]

@robertsLando Thanks, I’ll investigate the impact first. 🙏🏼

As a temporary mitigation, I may implement a simpler workaround by allowing indexed read/write paths in the encoder/decoder for large object properties.

[robertsLando]

It's ok 👍🏼