NO-JIRA: bump python bindings post-release version for PyPi release
1 file changed
tree: 495b13b772655904459c35cca64dbd3bf7249cc2
  1. bin/
  2. contrib/
  3. design/
  4. docs/
  5. examples/
  6. proton-c/
  7. proton-j/
  8. tests/
  9. tools/
  10. .gitattributes
  11. .gitignore
  12. .mailmap
  13. .travis.yml
  14. appveyor.yml
  15. CMakeLists.txt
  18. cpp.cmake
  22. NOTICE
  23. pom.xml
  26. TODO
  27. version.txt

Qpid Proton - AMQP messaging toolkit

Linux BuildWindows Build
Linux Build StatusWindows Build Status

Qpid Proton is a high-performance, lightweight messaging library. It can be used in the widest range of messaging applications, including brokers, client libraries, routers, bridges, proxies, and more. Proton makes it trivial to integrate with the AMQP 1.0 ecosystem from any platform, environment, or language


  • A flexible and capable reactive messaging API
  • Full control of AMQP 1.0 protocol semantics
  • Portable C implementation with bindings to popular languages
  • Pure-Java and pure-JavaScript implementations
  • Peer-to-peer and brokered messaging
  • Secure communication via SSL and SASL

Universal - Proton is designed to scale both up and down. Equally suitable for simple clients or high-powered servers, it can be deployed in simple peer-to-peer configurations or as part of a global federated messaging network.

Embeddable - Proton is carefully written to be portable and cross platform. It has minimal dependencies, and it is architected to be usable with any threading model, as well as with non-threaded applications. These features make it uniquely suited for embedding messaging capabilities into existing software.

Standard - Built around the AMQP 1.0 messaging standard, Proton is not only ideal for building out your own messaging applications but also for connecting them to the broader ecosystem of AMQP 1.0-based messaging applications.

Getting Started

See the included INSTALL file for build and install instructions and the DEVELOPERS file for information on how to modify and test the library code itself.

Please see for a more info.