You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2009/11/09 15:06:52 UTC
[jira] Created: (CAMEL-2151) Introduce asyncTo in the DSL to
support non blocking request/reply conversations
Introduce asyncTo in the DSL to support non blocking request/reply conversations
--------------------------------------------------------------------------------
Key: CAMEL-2151
URL: https://issues.apache.org/activemq/browse/CAMEL-2151
Project: Apache Camel
Issue Type: Sub-task
Components: camel-core
Affects Versions: 2.0.0
Reporter: Claus Ibsen
Assignee: Claus Ibsen
Fix For: 2.1.0
I guess a good and nice solution is to introduce a new variation of the {{to}} DSL for using async non blocking request / reply.
The problem if we just use {{to}} and have a special flag on the endpoint then its the Producer which needs to be handling the non blocking stuff and which is a bit more trickier to do than let it be a core part of the EIP processors in camel core. Then they will be able to setup a thread pool for the reply consumers and be able to _continue_ routing where the original exchange left.
As this is a generic solution it can help implement non blocking for other Camel components such as mina.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CAMEL-2151) Introduce asyncTo in the DSL to
support non blocking request/reply conversations
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-2151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=55258#action_55258 ]
Claus Ibsen commented on CAMEL-2151:
------------------------------------
trunk: 834417.
Multiple toAsync in same route
> Introduce asyncTo in the DSL to support non blocking request/reply conversations
> --------------------------------------------------------------------------------
>
> Key: CAMEL-2151
> URL: https://issues.apache.org/activemq/browse/CAMEL-2151
> Project: Apache Camel
> Issue Type: Sub-task
> Components: camel-core
> Affects Versions: 2.0.0
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: 2.1.0
>
>
> I guess a good and nice solution is to introduce a new variation of the {{to}} DSL for using async non blocking request / reply.
> The problem if we just use {{to}} and have a special flag on the endpoint then its the Producer which needs to be handling the non blocking stuff and which is a bit more trickier to do than let it be a core part of the EIP processors in camel core. Then they will be able to setup a thread pool for the reply consumers and be able to _continue_ routing where the original exchange left.
> As this is a generic solution it can help implement non blocking for other Camel components such as mina.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CAMEL-2151) Introduce asyncTo in the DSL to
support non blocking request/reply conversations
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-2151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen resolved CAMEL-2151.
--------------------------------
Resolution: Fixed
> Introduce asyncTo in the DSL to support non blocking request/reply conversations
> --------------------------------------------------------------------------------
>
> Key: CAMEL-2151
> URL: https://issues.apache.org/activemq/browse/CAMEL-2151
> Project: Apache Camel
> Issue Type: Sub-task
> Components: camel-core
> Affects Versions: 2.0.0
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: 2.1.0
>
>
> I guess a good and nice solution is to introduce a new variation of the {{to}} DSL for using async non blocking request / reply.
> The problem if we just use {{to}} and have a special flag on the endpoint then its the Producer which needs to be handling the non blocking stuff and which is a bit more trickier to do than let it be a core part of the EIP processors in camel core. Then they will be able to setup a thread pool for the reply consumers and be able to _continue_ routing where the original exchange left.
> As this is a generic solution it can help implement non blocking for other Camel components such as mina.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CAMEL-2151) Introduce asyncTo in the DSL to
support non blocking request/reply conversations
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-2151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=55257#action_55257 ]
Claus Ibsen commented on CAMEL-2151:
------------------------------------
trunk: 834396.
Added Spring DSL support and thread pool configuration in the Java DSL as well
> Introduce asyncTo in the DSL to support non blocking request/reply conversations
> --------------------------------------------------------------------------------
>
> Key: CAMEL-2151
> URL: https://issues.apache.org/activemq/browse/CAMEL-2151
> Project: Apache Camel
> Issue Type: Sub-task
> Components: camel-core
> Affects Versions: 2.0.0
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: 2.1.0
>
>
> I guess a good and nice solution is to introduce a new variation of the {{to}} DSL for using async non blocking request / reply.
> The problem if we just use {{to}} and have a special flag on the endpoint then its the Producer which needs to be handling the non blocking stuff and which is a bit more trickier to do than let it be a core part of the EIP processors in camel core. Then they will be able to setup a thread pool for the reply consumers and be able to _continue_ routing where the original exchange left.
> As this is a generic solution it can help implement non blocking for other Camel components such as mina.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CAMEL-2151) Introduce asyncTo in the DSL to
support non blocking request/reply conversations
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-2151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=55238#action_55238 ]
Claus Ibsen commented on CAMEL-2151:
------------------------------------
trunk: 834165.
Committed first work.
There are still a couple of issues in terms of naming, what the interfaces and methods should be called.
And a lot of {{toAsync}} is needed to be added in the DSL.
Also spring based unit tests should be done.
> Introduce asyncTo in the DSL to support non blocking request/reply conversations
> --------------------------------------------------------------------------------
>
> Key: CAMEL-2151
> URL: https://issues.apache.org/activemq/browse/CAMEL-2151
> Project: Apache Camel
> Issue Type: Sub-task
> Components: camel-core
> Affects Versions: 2.0.0
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: 2.1.0
>
>
> I guess a good and nice solution is to introduce a new variation of the {{to}} DSL for using async non blocking request / reply.
> The problem if we just use {{to}} and have a special flag on the endpoint then its the Producer which needs to be handling the non blocking stuff and which is a bit more trickier to do than let it be a core part of the EIP processors in camel core. Then they will be able to setup a thread pool for the reply consumers and be able to _continue_ routing where the original exchange left.
> As this is a generic solution it can help implement non blocking for other Camel components such as mina.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.