axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Asankha C. Perera (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AXIS2-2993) the async message receiver could use NIO
Date Fri, 27 Feb 2009 03:28:01 GMT

    [ https://issues.apache.org/jira/browse/AXIS2-2993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677236#action_12677236
] 

Asankha C. Perera commented on AXIS2-2993:
------------------------------------------

Hi Deepal

Lets take this concrete case as an example, why would one want to invoke the business logic
in another thread when the transports are built to inject messages with worker threads designed
"to do the work". I think I should have marked this issue as invalid instead?

thanks
asankha

> the async message receiver could use NIO
> ----------------------------------------
>
>                 Key: AXIS2-2993
>                 URL: https://issues.apache.org/jira/browse/AXIS2-2993
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Improvement
>          Components: kernel
>    Affects Versions: 1.2
>         Environment: all
>            Reporter: Michele Mazzucco
>            Assignee: Asankha C. Perera
>
> AbstractMessageReceiver does the job of deciding (based on the AbstractMessageReceiver.DO_ASYNC
property) whether or not to spin up a thread to do the work of invokeBusinessLogic(MessageContext).
What about using NIO instead?

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


Mime
View raw message