Author: jonathan
Date: Fri Nov 19 22:44:45 2010
New Revision: 1037071

URL: http://svn.apache.org/viewvc?rev=1037071&view=rev
Log:
Overview README.txt for the entire Qpid project.

Points people to the README.txt in the component directories. We need
to make sure each component directory has an adequate README.txt.

Added:
    qpid/trunk/qpid/README.txt

Added: qpid/trunk/qpid/README.txt
URL: 
http://svn.apache.org/viewvc/qpid/trunk/qpid/README.txt?rev=1037071&view=auto
==============================================================================
--- qpid/trunk/qpid/README.txt (added)
+++ qpid/trunk/qpid/README.txt Fri Nov 19 22:44:45 2010
@@ -0,0 +1,65 @@
+Apache Qpid is a high-speed, language independent, platform
+independent enterprise messaging system. It currently provides two
+messaging brokers (one implemented in C++, one implemented in Java),
+and messaging client libraries for Java JMS, C++, C# .NET, Python,
+Ruby, and WCF. The messaging protocol for Apache Qpid is AMQP
+(Advanced Message Queuing Protocol). You can read more about Qpid
+here:
+
+  http://qpid.apache.org/
+
+Documentation can be found here:
+
+  http://qpid.apache.org/documentation.html
+
+Qpid includes many components, which are built in various ways. Each
+component has a README.txt. Here are the subdirectories that contain
+the basic components:
+
+Messaging Broker (implemented in C++):
+
+  ./cpp
+
+Messaging Broker (implemented in Java):
+
+  ./java
+
+C++ Messaging Client Libraries
+
+  ./cpp
+
+Java JMS Client Libraries
+
+  ./java/client
+
+Python Client Libraries
+
+  ./python
+
+Ruby Client Libraries
+
+  ./ruby
+
+.NET Client Libraries
+
+  ./dotnet
+
+WCF Support
+
+  ./wcf
+
+Messaging Client (implemented in Ruby):
+
+  ./ruby
+
+Management Tools (implemented in Python):
+
+  ./tools
+
+Management Tools (implemented in Java):
+
+  ./java/management
+
+Documentation:
+
+  ./doc



---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:[email protected]

Reply via email to