I've taken some review comments and improved the picture a little. http://people.apache.org/~chug/QPID-0.8-Component-README.pdf
Where do you think is a good place in the source tree to check in the files QPID-0.8-Component-README .odg and .pdf? I'd like to see them in the source distro but they could go onto the wiki. -Chuck ----- "Jonathan Robie" <[email protected]> wrote: > From: "Jonathan Robie" <[email protected]> > To: [email protected] > Sent: Monday, November 22, 2010 5:37:29 PM GMT -05:00 US/Canada Eastern > Subject: Re: How easy is it to get Qpid going ? > > Yes, this is helpful. > > I've also tried to identify the "big picture" components in the new > qpid/README.txt. Perhaps we should check in your PDF and point to it > from qpid/README.txt? > > And if anyone wants to improve qpid/README.txt, please feel free! > > Jonathan > > On 11/22/2010 05:30 PM, Chuck Rolke wrote: > > oops, no attachment. > > > > http://people.apache.org/~chug/QPID-0.8-Component-Architecture.pdf > > > > -C > > > > ----- "Chuck Rolke"<[email protected]> wrote: > > > >> From: "Chuck Rolke"<[email protected]> > >> To: [email protected] > >> Sent: Monday, November 22, 2010 5:21:17 PM GMT -05:00 US/Canada > Eastern > >> Subject: Re: How easy is it to get Qpid going ? > >> > >> 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. > > --------------------------------------------------------------------- > 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]
