Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be unavailable on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 653532 - .NET Binding to C++ Messaging does not handle .NET arrays predictably.
Summary: .NET Binding to C++ Messaging does not handle .NET arrays predictably.
Keywords:
Status: NEW
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-sdk
Version: 1.3
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: ---
: ---
Assignee: Chuck Rolke
QA Contact: MRG Quality Engineering
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-15 16:56 UTC by Chuck Rolke
Modified: 2021-03-16 12:46 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Apache JIRA QPID-4797 0 None None None Never

Description Chuck Rolke 2010-11-15 16:56:06 UTC
Description of problem:

As implemented today .NET array handling could be improved.

The only data type that is handled as an array is System::Byte. In this case the .NET array is translated into an amqp string where the string's raw bytes come from the .NET array. While this interface is useful and should be preserved it is lacking support for sending the .NET byte array as an ampq/list.

Further, no other data type (string, float, bool, map, list, etc) is processed as an array. Reasonable users may expect to have .NET array<System::UInt64> to be be sent as an amqp/list of qpid::types::VAR_UINT64 without the overhead of packing the array into a .NET Collection<object>.

The same logic applies to received amqp/list messages. These could be returned as .NET array<ofSomeType> instead of as a .NET Collection<object>, with consequent performance improvement.

Version-Release number of selected component (if applicable):

1.3.0.18

How reproducible:

100%

Steps to Reproduce:
1. Attempt to set message content to array<System::Int32>.
2.
3.
  
Actual results:

Will not compile.

Expected results:

Compile succeeds. Receiving client receives an amqp/list of Int32.

Additional info:

Comment 1 Justin Ross 2011-05-19 19:56:13 UTC
Chuck, is there a related jira?

Comment 2 Chuck Rolke 2013-05-01 14:33:48 UTC
This issue derives from initial discussions upstream in https://issues.apache.org/jira/browse/QPID-2589


Note You need to log in before you can comment on or make changes to this bug.