Mailing-List: contact dev-help@zest.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@zest.apache.org
Date: Wed, 17 Jun 2015 14:08:00 +0000 (UTC)
From: "Niclas Hedhman (JIRA)" <jira@apache.org>
To: dev@zest.apache.org
Message-ID: <JIRA.12838482.1434550023000.96338.1434550080334@Atlassian.JIRA>
In-Reply-To: <JIRA.12838482.1434550023000@Atlassian.JIRA>
References: <JIRA.12838482.1434550023000@Atlassian.JIRA>
 <JIRA.12838482.1434550023147@arcas>
Subject: [jira] [Created] (ZEST-32) Messaging SPI and Extension
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Niclas Hedhman created ZEST-32:
----------------------------------

             Summary: Messaging SPI and Extension
                 Key: ZEST-32
                 URL: https://issues.apache.org/jira/browse/ZEST-32
             Project: Zest
          Issue Type: Bug
            Reporter: Niclas Hedhman


Just like we have an reasonably good abstraction for Storage, with EntityComposites, UnitOfWork and EntityStores to fulfill that, we should try to create a similar abstract for Messaging.

Bring this up on the dev@ list created a lot of responses, so I assume that there is great interest and people are eager to contribute in any way they can, as it is a topic dear to the heart.

Before going down a particular mode of thinking about the implementation, I want this ticket to be filled with as many crazy ideas as possible in the Comments below.

PLEASE, one idea per Comment, and any discussion about such idea, please bring that to the dev@ list, and update the comment later if needed.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)