This is an automated email from the ASF dual-hosted git repository.

rombert pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/sling-org-apache-sling-mom.git

commit 19d2a5f9528de4e80d3c90a5151c6ce0884baca9
Author: Oliver Lietz <[email protected]>
AuthorDate: Tue Oct 3 10:02:16 2017 +0000

    SLING-7167 Adjust READMEs
    
    add uniform header linking to Sling project
    
    git-svn-id: https://svn.apache.org/repos/asf/sling/trunk@1810888 
13f79535-47bb-0310-9956-ffa450edef68
---
 README.md | 10 +++++++---
 1 file changed, 7 insertions(+), 3 deletions(-)

diff --git a/README.md b/README.md
index 311c22b..15b8c31 100644
--- a/README.md
+++ b/README.md
@@ -1,4 +1,8 @@
-# Message Oriented Middleware API ( or message passing API).
+# Apache Sling Message oriented Middleware API
+
+This module is part of the [Apache Sling](https://sling.apache.org) project.
+
+## Message Oriented Middleware API ( or message passing API).
 
 This bundle contains an API to support 2 types of message passing. Pub/Sub and 
Queue.
 Pub/Sub message passing supports the publication of messages to multiple 
subscribers. Queue 
@@ -7,7 +11,7 @@ organised by a Topic name. Queues are named. There are no 
implementation details
 bundle and no bindings to any one MoM implementation, although it is expected 
that this 
 API could be implemented over either JMS or a AMQP client.
 
-# Publish Subscribe
+## Publish Subscribe
 
 Messages that are sent to a topic by publishing are received by all 
subscribers that were active at the time the message is published.
 
@@ -30,7 +34,7 @@ To subscribe to a topic the caller must also use the 
[TopicManager API](src/main
           
 The API does not impose any stcuture on topic names, but the underlying 
implementation might.
 
-# Queue
+## Queue
 
 A Queue implementation guarantees that messages will be delivered to one and 
only once QueueReader
 in the order in which the messages were added to the Queue. The QueueReader 
implementation may

-- 
To stop receiving notification emails like this one, please contact
"[email protected]" <[email protected]>.

Reply via email to