tree: 8fa025ecbddabc71dd1e4699721f2049b7e2c436 [path history] [tgz]
  1. .appveyor.yml
  2. .gitattributes
  3. .gitignore
  4. .mailmap
  5. .reviewboardrc
  6. .travis.yml
  7. CMakeLists.txt
  8. INSTALL.md
  9. LICENSE.txt
  10. NOTICE.txt
  11. README.md
  12. VERSION.txt
  13. c/
  14. cpp/
  15. docs/
  16. go/
  17. misc/
  18. python/
  19. ruby/
  20. scripts/
  21. tests/
  22. tools/
README.md

Qpid Proton - AMQP messaging toolkit

Linux/OSX BuildWindows Build
Linux/OSX 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

Features

  • A flexible and capable reactive messaging API
  • Full control of AMQP 1.0 protocol semantics
  • Portable C implementation with bindings to popular languages
  • 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.

Please see https://qpid.apache.org/proton for more information.

Getting Started

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