[jira] [Commented] (PROTON-322) Extend the native Ruby array and hash classes to work with the Data type

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/PROTON-322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13671704#comment-13671704 ] 

ASF subversion and git services commented on PROTON-322:
--------------------------------------------------------

Commit 1488342 from mcpierce
[ https://svn.apache.org/r1488342 ]

PROTON-322: Extended the Ruby Array class to work with the Data class.

Added attributes for setting the Proton type and description for
encoding an entire array as a described Array. If the type isn't set
then the array is added as an AMQP List instead.
                
> Extend the native Ruby array and hash classes to work with the Data type
> ------------------------------------------------------------------------
>
>                 Key: PROTON-322
>                 URL: https://issues.apache.org/jira/browse/PROTON-322
>             Project: Qpid Proton
>          Issue Type: Improvement
>          Components: proton-c
>            Reporter: Darryl L. Pierce
>            Assignee: Darryl L. Pierce
>
> 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.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira