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.


git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk@1037071 13f79535-47bb-0310-9956-ffa450edef68

1 files changed, 65 insertions, 0 deletions

diff --git a/qpid/README.txt b/qpid/README.txt
new file mode 100644
index 0000000000..14202ab703
--- /dev/null
+++ b/qpid/README.txt
@@ -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