I'd like to contribute a picture or two. Please comment on the current attachement.
I'm trying to show how the parts relate to each other. I'm most familiar with the Cpp block so I'm most sure of what's going on in that part. My understandings are: 1. The Java stack goes end to end with no support required from Cpp. 2. WCF uses xarm (transaction resource manager) and the client, no messaging. 3. Python and Ruby QMF clients use the C++ QMF binding. 4. Python, Ruby, and .NET QPID clients use the C++ QPID binding. 5. Top level DOTNET client uses nothing from Cpp and is being deprecated. 6. Top level Python client uses nothing from Cpp but still works. It is probably not as great a choice as the Python Qpid binding for performance reasons. It should be kept as a/the reference implementation. 7. Top level Ruby client is being deprecated. I could use help showing relationships inside the Java box. I think that if this one picture were broken into maybe five with each showing different levels of detail it would be useful. Regards, Chuck ----- "Jonathan Robie" <[email protected]> wrote: > From: "Jonathan Robie" <[email protected]> > To: [email protected] > Sent: Monday, November 22, 2010 2:27:35 PM GMT -05:00 US/Canada Eastern > Subject: Re: How easy is it to get Qpid going ? > > On 11/22/2010 02:15 PM, Jonathan Robie wrote: > > > Most of us work directly with the source tree, so we know that > works. > > We also need to make the source tree more accessible. The new > top-level > README.txt at least identifies which components can be found in the > source tree, and points to their README.txt files. If we continue the > > path top-down so that each component clearly says how to build it, and > > gives some overview, that should help a great deal. > > And I don't think that would take that much work. But the people > responsible for each component should do that. > > Jonathan > > --------------------------------------------------------------------- > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:[email protected]
--------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
