Menu Search

Qpid Proton 0.5 Release Notes

Proton is a high-performance, lightweight messaging library. More about Qpid Proton.

For more information about this release, including download links and documentation, see the release overview.

New features and improvements

  • PROTON-160 - Allow open.hostname to be configured independently of network hostname
  • PROTON-225 - Redesign Transport interface such that Transport owns the in/out buffers rather than its client
  • PROTON-227 - Ruby bindings need a Data class
  • PROTON-228 - Perl bindings need a Data class
  • PROTON-229 - allow messenger to not put the address on the message
  • PROTON-231 - Allow messenger to be used inside an event loop
  • PROTON-257 - Add example to illustrate use of proton-j API
  • PROTON-270 - Make artifactId for proton tests more descriptive
  • PROTON-280 - Maven should generate project documentation including markdown docs
  • PROTON-294 - Driver - Enable TCP_NODELAY on connections by default (posix)
  • PROTON-307 - Remove redundant input and output methods from Sasl interface
  • PROTON-316 - Developers need clearer instructions for working in a development environment
  • PROTON-317 - Feature Enhancement - API Exposure of underlying references to internal atoms
  • PROTON-320 - [Proton-J] use varargs for Sasl#setMechanisms()
  • PROTON-322 - Extend the native Ruby array and hash classes to work with the Data type
  • PROTON-324 - Perl arrays can be easily extracted from a Data object.
  • PROTON-328 - Provide utility method for extracting hashes out of a Perl Data object.
  • PROTON-349 - Driver connector needs an accessor for the "name" field
  • PROTON-367 - Provide Ruby post, fetch and mailserver examples
  • PROTON-369 - Ruby: Message class does not have a properties property
  • PROTON-378 - Ruby Message object does not include instructions property.
  • PROTON-379 - Ruby Message object does not include annotations property
  • PROTON-380 - Ruby Message object does not include a body property.

Bugs fixed

  • PROTON-116 - Proton sends explicit disposition for pre-settled messages
  • PROTON-121 - Platform specific code is mixed in with platform independent code
  • PROTON-139 - Can't set distribution-mode on a source
  • PROTON-212 - Windows snprintf and vsnprintf differ on overflow from C99
  • PROTON-214 - Test "proton_tests.messenger.MessengerTest.testSendBogus" failed
  • PROTON-249 - Build fails on Win8 / VS 2012 with path error
  • PROTON-263 - JNIDelivery.isPartial should delegate to pn_delivery_partial
  • PROTON-264 - Proton-J and Proton-C transports make inconsistent use of return values within methods input and output
  • PROTON-266 - JNIMessage does not encode message body
  • PROTON-267 - Driver ignores socket close event code returned from socket read/write
  • PROTON-268 - Messenger hang in pn_messenger_stop()
  • PROTON-269 - Connect Redirect parsing incorrectly uses position in map rather than value of key
  • PROTON-271 - proton-hawtdispatch transport not properly encoding PLAIN sasl user/password.
  • PROTON-275 - Restore Windows basic build
  • PROTON-276 - Ssl tests fail against proton-j on Windows (tests can't find certificates)
  • PROTON-277 - dynamic flag on source/target is not handled correctly
  • PROTON-279 - cmake tests don't actually fail even when python tests are failing
  • PROTON-286 - Windows driver hangs on pending connection close
  • PROTON-295 - recv(-1) + incoming_window == bad
  • PROTON-297 - 100% CPU usage on ARM in pn_messenger_recv()
  • PROTON-304 - Remove accept mode from Ruby bindings
  • PROTON-305 - Remove accept mode from Perl bindings
  • PROTON-306 - Ruby List helper class does not properly put values from Data class
  • PROTON-314 - Posix driver - If a connector is spuriously activated for write, the system will spin, consuming cpu
  • PROTON-315 - proton-j Messenger testIncomingQueueBiggerThanWindow failing
  • PROTON-318 - [Proton-J] the SaslImpl state field is not updated to reflect the outcome for the client role
  • PROTON-325 - Python lists are truncated when None is encountered
  • PROTON-331 - session window confuses frames and deliveries
  • PROTON-336 - pn_messenger_put does not clear PN_OVERFLOW error after expanding its buffer
  • PROTON-340 - AMQP to JMS transformer fails to properly map AMQP specific property types like UnsignedInteger
  • PROTON-341 - Ruby fails the integration tests
  • PROTON-350 - Messenger - pn_messenger_recv( -1 ) does not flow control senders
  • PROTON-351 - Proton-J engine violates link credit window
  • PROTON-352 - Ruby test errors
  • PROTON-354 - TrackerQueue window pointers could wrap. Increase numeric range or use modular arithmatic
  • PROTON-355 - Fix broken Ruby Rspec tests
  • PROTON-360 - [proton-j][hawtdispatch] Add support for ANONYMOUS SASL
  • PROTON-361 - [proton-j][hawtdispatch] transport is silently discarding errors while connecting
  • PROTON-362 - Fix compilation on OS X
  • PROTON-364 - None of Proton's examples are installed.
  • PROTON-365 - PHP bindings are missing the disposition API calls
  • PROTON-368 - Calling pn_messenger_put with a message with no address causes a segmentation fault
  • PROTON-372 - driver does not handle POLLHUP
  • PROTON-376 - Ruby does not properly encode a map into a Data instance.
  • PROTON-377 - Ruby Data does not encode an instance of ::Time
  • PROTON-381 - Mapping doesn't properly handle symbols in Ruby.
  • PROTON-387 - Linked list utility code leaves dangling pointers in removed node.
  • PROTON-389 - Messenger asserts if it receives a RELEASED disposition
  • PROTON-393 - messenger needs a way to reset the error
  • PROTON-394 - Exhausting credit on a link can affect other links using the same session.
  • PROTON-396 - Proton Messenger should configure the SNI headers on it's TLS connections so that those connections can be routed by SNI aware proxies.
  • PROTON-399 - 'Make install' doesn't install ruby qpid_proton
  • PROTON-400 - 'Make install' doesn't install perl qpid_proton
  • PROTON-402 - [proton-c] Example proton.c with no args causes segmentation fault
  • PROTON-403 - java transport interface has no way of communicating end of stream conditions
  • PROTON-404 - multiple links on a single session cause duplicate delivery-ids
  • PROTON-406 - Cmake build fails to find Ruby vendor location on some platforms
  • PROTON-60 - Support configuring the max frame size.
  • PROTON-61 - Need a means of specifying and reading connection capabilities & properties
  • PROTON-81 - Expose send/receive settle modes
  • PROTON-97 - RELEASED disposition not processed by engine

Tasks

None