AimDB **v2.0.0** is out — our first major release since 1.0. #258
lxsaah
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Every transport now speaks one wire protocol (AimX 3.0): the separate WebSocket protocol crate is gone and the browser bridge, UDS, serial and TCP all ride the same session engine. The runtime generic
Ris out of the public API. Three new transports ship:aimdb-uds-connector,aimdb-serial-connector,aimdb-tcp-connector.This is a breaking release.
PROTOCOL_VERSIONmoves2.0→3.0and the handshake now negotiates it, so a pre-3.0 client is refused athello. Upgrade servers and clients together — there's a seven-step migration guide in the notes:Release notes & migration guide
Thank you
@thaodt built the TCP transport — one of the three new crates — plus the codec work behind per-link format selection (#166, #171, #176, #180, #183, #203).
@solus161 got
aimdb-syncoffstdso the blocking facade builds on embedded (#204, #205), fixed a leak where dropped streams left entries behind (#218), and enforcedwith_max_clients(#249).@harunugurlu wrote the sync API characterization tests (#211) — the unglamorous work that made a refactor this size survivable — plus two examples (#182, #191).
And thanks to everyone else who contributed to this release.
Thank you all.
Upgrade trouble or anything odd after moving to 3.0, reply here or open an issue.
All reactions