On 05/14/2010 11:37 PM, Chuck Rolke wrote:
I must apologize for my part in sticking this code into the code base
before a proper discussion.
Chuck,
you didn't stick the code into the codebase, you attached a patch
demonstrating an interesting (and in my view valuable) approach to a
Jira. I think that is a reasonable approach and indeed it elicited a
comment on the Jira before it was committed.
I fell into the logic trap that the idea
behind the work "made sense" so I went ahead. I neglected the larger
group by thinking that it "made sense to me" without having everyone
else's thoughts. Sorry about that.
We are all guilty of this on occasion.
My purpose in starting this thread was not to point fingers (not even at
Ted ;-) but to try and force some debate and build some consensus on the
way forward. We want to combine our efforts and we can only do that if
we have a common understanding of where we want to go.
Please, though, don't be "hacked off". If I'd have gone in to the
WCF project and started wailing away on the code without a buy-in
then someone could legitimately be upset. The C++ messaging interface
is new and WCF will probably never give you direct access to it.
I don't see there being any conflict between the in-the-small
.net binding and the in-the-large WCF messaging scheme.
They coexist naturally.
I think that misses the point to some extent though. We need to
rationalise the various contributed solutions for the .net platform into
something that we feel comfortable maintaining going forward and for
which we can offer users the expected degree of support. This requires
that every component has the community behind it, not just an individual.
One important question is if/when/why we would recommend that a user
choose to write their code to this interface rather than the WCF channel
interface. Can we articulate why directly using the messaging API would
valuable for .net users?
--Gordon.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
