Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
Description
Currently Ruby developers have to explicitly create instances of either Qpid::Proton::Data::List, Qpid::Proton::Data::Array or Qpid::Proton::Data::Map to get access to helper methods for interaction with Qpid::Proton::Data. But this too tightly couples the user to Proton-specific code for non-messaging related functions.
Instead, we should leverage Ruby metaprogramming and add the needed functions to the standard Ruby classes directly. That way developers wouldn't need to refactor existing code to work with Proton.