larvit/smpp-js
3
0
Fork 0
Code Issues Pull Requests 1 Actions Activity

Say in the Audience section that the store has not shipped
Mirror / push (push) Successful in 6s
Details
Test / lint (pull_request) Successful in 25s
Details
Test / test (18) (pull_request) Successful in 32s
Details
Test / test (20) (pull_request) Successful in 32s
Details
Test / test (22) (pull_request) Successful in 32s
Details
Test / test (24) (pull_request) Successful in 31s
Details
Test / test (26) (pull_request) Successful in 32s
Details

Browse Source
This commit is contained in:
Lilleman auf Larv
2026-09-28 21:01:23 +02:00
parent e8248e6b9c
commit a66ff636a2
2 changed files with 5 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+3 -2
View File
@@ -743,8 +743,9 @@ Who depends on this library, and what they may rely on.
- **The developer building the SMPP edge of something else.** What binds to `server()` in practice is
an aggregator's customer-facing edge, a bridge putting SMPP in front of a modern transport, or a
test double standing in for an SMSC. This is not a store-and-forward SMSC and will not become one:
spooling, scheduling, retry policy and billing belong to whatever this is the edge of, and state
shared between instances goes through the store in goal 9.
spooling, scheduling, retry policy and billing belong to whatever this is the edge of. State shared
between instances is for goal 9's store, which has not shipped: today every session keeps its own,
in memory.
- **Pre-1.0, so the minor is the breaking unit** and a patch never breaks. What a 0.4.0 consumer has
to change is in [MIGRATION.md](https://gitea.larvit.se/larvit/smpp-js/src/branch/main/MIGRATION.md);
what each later minor changes is in