qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrea Gazzarini (JIRA)" <qpid-...@incubator.apache.org>
Subject [jira] Created: (QPID-1664) Asynchronous notification capability
Date Sat, 14 Feb 2009 10:47:59 GMT
Asynchronous notification capability
------------------------------------

                 Key: QPID-1664
                 URL: https://issues.apache.org/jira/browse/QPID-1664
             Project: Qpid
          Issue Type: Sub-task
          Components: Java Management : QMan
    Affects Versions: M5
         Environment: J2SE 1.5 or higher
            Reporter: Andrea Gazzarini
            Assignee: Andrea Gazzarini
            Priority: Critical
             Fix For: M5


The current implementation of WS-Notification engine is synchronous. That means the publisher
(QMan) will remain blocked until the notification has been processed on oberserver (client)
side...this is in generarl not acceptable because a server component depends on a client behaviour...
So, notifications should be processed in separate threads. JDK 1.5 introduced a TrheadPoolEXecutor
that is something like a WorkManager in a JEE environment. 
Qman will use it for asynchronous notification capability.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org


Mime
View raw message