Qpid
  1. Qpid
  2. QPID-2646

Qpid Messaging address support for WCF Channel

    Details

    • Type: New Feature New Feature
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 0.7
    • Fix Version/s: 0.7
    • Component/s: WCF/C++ Client
    • Labels:
      None
    • Environment:

      Windows

      Description

      Updating the WCF channel to handle the same address strings as the C++ client is desirable for consistency between clients and also simplifies rebasing the WCF channel on the new messaging API in the future.

      This JIRA can be used to track functionality as it becomes available in the 0.7 timeframe.

      1. QPID-2646-2.patch
        30 kB
        Cliff Jansen
      2. QPID-2646-1.patch
        25 kB
        Cliff Jansen

        Activity

        Hide
        Cliff Jansen added a comment -

        This patch provides Drain and Spout programs that operate like their existing counterparts in C++ and Python. These programs can be used to monitor the progress of addressing functionality in the WCF Channel. They can also be enhanced going forward to track map message support (coming soon).

        Show
        Cliff Jansen added a comment - This patch provides Drain and Spout programs that operate like their existing counterparts in C++ and Python. These programs can be used to monitor the progress of addressing functionality in the WCF Channel. They can also be enhanced going forward to track map message support (coming soon).
        Hide
        Cliff Jansen added a comment -

        This patch provides updates to the transport channel and Interop layer to create temporary queues (bound to an exchange), point and shoot queues (default exchange), and browse mode. Other advanced address options such as node/link properties and assert are not yet implemented. Use of unimplemented addressing features results in an ArgumenException from the WCF Channel for now.

        Show
        Cliff Jansen added a comment - This patch provides updates to the transport channel and Interop layer to create temporary queues (bound to an exchange), point and shoot queues (default exchange), and browse mode. Other advanced address options such as node/link properties and assert are not yet implemented. Use of unimplemented addressing features results in an ArgumenException from the WCF Channel for now.
        Hide
        Ted Ross added a comment -

        My understanding of the issues here may be limited, but it seems that you are going to a lot of work to adapt the new addressing syntax to the old C++ API when the new C++ API already implements all of the new addressing. Might it be simpler to port over to the new API and leverage its capabilities?

        I'm not sure if it's helpful to you, but the new C++ API (and its addressing, and map-message support) are now also available via .NET using the .NET binding Chuck Rolke contributed.

        -Ted

        Show
        Ted Ross added a comment - My understanding of the issues here may be limited, but it seems that you are going to a lot of work to adapt the new addressing syntax to the old C++ API when the new C++ API already implements all of the new addressing. Might it be simpler to port over to the new API and leverage its capabilities? I'm not sure if it's helpful to you, but the new C++ API (and its addressing, and map-message support) are now also available via .NET using the .NET binding Chuck Rolke contributed. -Ted
        Hide
        Cliff Jansen added a comment -

        Please see the comments attached to QPID-2589.

        The bottom line is that the underlying new C++ messaging API provides less functionality than the older client API for 0-10 in a number of important areas. The .NET binding is necessarily similarly constrained.

        As I understand it, there is a desire to eventually enhance the C++ API to provide the missing bits described in the thread. But in the 0.7 time frame, this appears to be the most sensible route to add the functionality and simultaneously ease the future switch to the messaging C++ API.

        Show
        Cliff Jansen added a comment - Please see the comments attached to QPID-2589 . The bottom line is that the underlying new C++ messaging API provides less functionality than the older client API for 0-10 in a number of important areas. The .NET binding is necessarily similarly constrained. As I understand it, there is a desire to eventually enhance the C++ API to provide the missing bits described in the thread. But in the 0.7 time frame, this appears to be the most sensible route to add the functionality and simultaneously ease the future switch to the messaging C++ API.
        Hide
        Steve Huston added a comment -

        Assigning this to Cliff - he's a committer now (wasn't when this jira was entered). Cliff, could you please address or rescope to 0.9?

        Show
        Steve Huston added a comment - Assigning this to Cliff - he's a committer now (wasn't when this jira was entered). Cliff, could you please address or rescope to 0.9?
        Hide
        Cliff Jansen added a comment -

        Fixed on trunk r1026915.

        Show
        Cliff Jansen added a comment - Fixed on trunk r1026915.

          People

          • Assignee:
            Cliff Jansen
            Reporter:
            Cliff Jansen
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development