v1.0.0
🚀 SIPgo v1.0.0 is here 🚀
SIPgo had a long journey, and API was challenged with many different projects and used by big names out there. There hasn’t been any significant need for breaking changes lately, so there is pretty high confidence this API will remain stable going forward.
What does 1.0.0 mean?
- A stable and predictable API
- No breaking changes planned in the near future
- It will make more stable API for Diago lib
- More Confidence for production deployments
Future ✈️
There are open things regarding performance and small features that will probably land into 1.0.0 API. To mentioned few
- PR for Parser improvements
- Gracefull shutdown
- Transport more control like deadlines
Lib has opportunity to be more improved but even with current state it excels in performance of handling high loads of traffic.
You can always check proxysip example and running locally with docker-compose sipp stress where on this limited container (4 cores) we can achieve high throughput on modern CPU ~2000rps with no latency impact.
✋ v2
Many Big things or issues that we may not be good fit for current API are moved to v2 Milestone and I would like to see this happening as well.
🙌 Thank You
Huge thanks to everyone who contributed, submitted issues, provided feedback, or used SIPgo as a building block in their own systems.
Your input has shaped the API and helped bring SIPgo to this milestone.
Thank you all for your contributions and for keeping this project alive!
What's Changed
- fix: ParserStream handling StartLine and incomplete Header by @j-licht in #255
- fix according RFC3261 12.1 Creation of a Dialog by @zusrut in #262
New Contributors
Full Changelog: v0.33.0...v1.0.0
