You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@synapse.apache.org by "Supun Kamburugamuva (JIRA)" <ji...@apache.org> on 2010/02/10 06:16:28 UTC
[jira] Created: (SYNAPSE-608) Priority based mediation
Priority based mediation
------------------------
Key: SYNAPSE-608
URL: https://issues.apache.org/jira/browse/SYNAPSE-608
Project: Synapse
Issue Type: New Feature
Reporter: Supun Kamburugamuva
Priority based mediation allows users to execute sequences with a given priority. This is important when there is a high volume of traffic going through synapse which require different processing capabilities.
First I'll explain the problem.
Lets assume we have two types of messages coming in to the ESB. One type of message(P1) is very important and other type(P2) is not that important. User can afford to loose some of the P2 messages occasionally. Load characteristics of both messages change over time. Some time lots of P1 and few P2 messages can come. Sometimes lots of P2 messages with few P2 messages can come. Sometimes lots of P1 and P2 messages can come.
In all these scenarios synapse should be able to guarantee the processing of P1 messages, even if it loose some P2 messages.
To get this functionality in to ESB, we have implemented this feature in to synapse at two different levels. They are at HTTP transport level and mediation level.
In the mediation level user can filter the messages using normal synapse capabilities for determining the priority and execute a sequence with a given priority.
In the transport level there is a configuration to determine the priority from HTTP properties and execute the sequences accordingly.
This feature is totally optional.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Assigned: (SYNAPSE-608) Priority based mediation
Posted by "Ruwan Linton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ruwan Linton reassigned SYNAPSE-608:
------------------------------------
Assignee: Ruwan Linton
> Priority based mediation
> ------------------------
>
> Key: SYNAPSE-608
> URL: https://issues.apache.org/jira/browse/SYNAPSE-608
> Project: Synapse
> Issue Type: New Feature
> Reporter: Supun Kamburugamuva
> Assignee: Ruwan Linton
> Attachments: SYNAPSE-608.patch
>
>
> Priority based mediation allows users to execute sequences with a given priority. This is important when there is a high volume of traffic going through synapse which require different processing capabilities.
> First I'll explain the problem.
> Lets assume we have two types of messages coming in to the ESB. One type of message(P1) is very important and other type(P2) is not that important. User can afford to loose some of the P2 messages occasionally. Load characteristics of both messages change over time. Some time lots of P1 and few P2 messages can come. Sometimes lots of P2 messages with few P2 messages can come. Sometimes lots of P1 and P2 messages can come.
> In all these scenarios synapse should be able to guarantee the processing of P1 messages, even if it loose some P2 messages.
> To get this functionality in to ESB, we have implemented this feature in to synapse at two different levels. They are at HTTP transport level and mediation level.
> In the mediation level user can filter the messages using normal synapse capabilities for determining the priority and execute a sequence with a given priority.
> In the transport level there is a configuration to determine the priority from HTTP properties and execute the sequences accordingly.
> This feature is totally optional.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Updated: (SYNAPSE-608) Priority based mediation
Posted by "Supun Kamburugamuva (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Supun Kamburugamuva updated SYNAPSE-608:
----------------------------------------
Attachment: (was: SYNAPSE-608.patch)
> Priority based mediation
> ------------------------
>
> Key: SYNAPSE-608
> URL: https://issues.apache.org/jira/browse/SYNAPSE-608
> Project: Synapse
> Issue Type: New Feature
> Reporter: Supun Kamburugamuva
> Attachments: SYNAPSE-608.patch
>
>
> Priority based mediation allows users to execute sequences with a given priority. This is important when there is a high volume of traffic going through synapse which require different processing capabilities.
> First I'll explain the problem.
> Lets assume we have two types of messages coming in to the ESB. One type of message(P1) is very important and other type(P2) is not that important. User can afford to loose some of the P2 messages occasionally. Load characteristics of both messages change over time. Some time lots of P1 and few P2 messages can come. Sometimes lots of P2 messages with few P2 messages can come. Sometimes lots of P1 and P2 messages can come.
> In all these scenarios synapse should be able to guarantee the processing of P1 messages, even if it loose some P2 messages.
> To get this functionality in to ESB, we have implemented this feature in to synapse at two different levels. They are at HTTP transport level and mediation level.
> In the mediation level user can filter the messages using normal synapse capabilities for determining the priority and execute a sequence with a given priority.
> In the transport level there is a configuration to determine the priority from HTTP properties and execute the sequences accordingly.
> This feature is totally optional.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Updated: (SYNAPSE-608) Priority based mediation
Posted by "Supun Kamburugamuva (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Supun Kamburugamuva updated SYNAPSE-608:
----------------------------------------
Attachment: Priority_Based_Mediation_Configuration.pdf
priority-configuration.xml
synapse_sample_150.xml
Attaching the configuration documentation and some samples.
User can specify the priority-configuration.xml as a parameter in the NHTTP transport configuration. Parameter name is priorityConfigFile.
Thanks,
Supun..
> Priority based mediation
> ------------------------
>
> Key: SYNAPSE-608
> URL: https://issues.apache.org/jira/browse/SYNAPSE-608
> Project: Synapse
> Issue Type: New Feature
> Reporter: Supun Kamburugamuva
> Assignee: Ruwan Linton
> Attachments: priority-configuration.xml, Priority_Based_Mediation_Configuration.pdf, SYNAPSE-608.patch, synapse_sample_150.xml
>
>
> Priority based mediation allows users to execute sequences with a given priority. This is important when there is a high volume of traffic going through synapse which require different processing capabilities.
> First I'll explain the problem.
> Lets assume we have two types of messages coming in to the ESB. One type of message(P1) is very important and other type(P2) is not that important. User can afford to loose some of the P2 messages occasionally. Load characteristics of both messages change over time. Some time lots of P1 and few P2 messages can come. Sometimes lots of P2 messages with few P2 messages can come. Sometimes lots of P1 and P2 messages can come.
> In all these scenarios synapse should be able to guarantee the processing of P1 messages, even if it loose some P2 messages.
> To get this functionality in to ESB, we have implemented this feature in to synapse at two different levels. They are at HTTP transport level and mediation level.
> In the mediation level user can filter the messages using normal synapse capabilities for determining the priority and execute a sequence with a given priority.
> In the transport level there is a configuration to determine the priority from HTTP properties and execute the sequences accordingly.
> This feature is totally optional.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Updated: (SYNAPSE-608) Priority based mediation
Posted by "Supun Kamburugamuva (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Supun Kamburugamuva updated SYNAPSE-608:
----------------------------------------
Attachment: SYNAPSE-608-Sample-documentation.patch
> Priority based mediation
> ------------------------
>
> Key: SYNAPSE-608
> URL: https://issues.apache.org/jira/browse/SYNAPSE-608
> Project: Synapse
> Issue Type: New Feature
> Reporter: Supun Kamburugamuva
> Assignee: Ruwan Linton
> Attachments: priority-configuration.xml, Priority_Based_Mediation_Configuration.pdf, SYNAPSE-608-Sample-documentation.patch, SYNAPSE-608-samples.patch, SYNAPSE-608.patch, synapse_sample_150.xml
>
>
> Priority based mediation allows users to execute sequences with a given priority. This is important when there is a high volume of traffic going through synapse which require different processing capabilities.
> First I'll explain the problem.
> Lets assume we have two types of messages coming in to the ESB. One type of message(P1) is very important and other type(P2) is not that important. User can afford to loose some of the P2 messages occasionally. Load characteristics of both messages change over time. Some time lots of P1 and few P2 messages can come. Sometimes lots of P2 messages with few P2 messages can come. Sometimes lots of P1 and P2 messages can come.
> In all these scenarios synapse should be able to guarantee the processing of P1 messages, even if it loose some P2 messages.
> To get this functionality in to ESB, we have implemented this feature in to synapse at two different levels. They are at HTTP transport level and mediation level.
> In the mediation level user can filter the messages using normal synapse capabilities for determining the priority and execute a sequence with a given priority.
> In the transport level there is a configuration to determine the priority from HTTP properties and execute the sequences accordingly.
> This feature is totally optional.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Resolved: (SYNAPSE-608) Priority based mediation
Posted by "Ruwan Linton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ruwan Linton resolved SYNAPSE-608.
----------------------------------
Resolution: Fixed
Fix Version/s: NIGHTLY
Thanks Supun, I have applied the documentation patches as well.
Ruwan
> Priority based mediation
> ------------------------
>
> Key: SYNAPSE-608
> URL: https://issues.apache.org/jira/browse/SYNAPSE-608
> Project: Synapse
> Issue Type: New Feature
> Reporter: Supun Kamburugamuva
> Assignee: Ruwan Linton
> Fix For: NIGHTLY
>
> Attachments: priority-configuration.xml, Priority_Based_Mediation_Configuration.pdf, SYNAPSE-608-Sample-documentation.patch, SYNAPSE-608-samples.patch, SYNAPSE-608.patch, synapse_sample_150.xml
>
>
> Priority based mediation allows users to execute sequences with a given priority. This is important when there is a high volume of traffic going through synapse which require different processing capabilities.
> First I'll explain the problem.
> Lets assume we have two types of messages coming in to the ESB. One type of message(P1) is very important and other type(P2) is not that important. User can afford to loose some of the P2 messages occasionally. Load characteristics of both messages change over time. Some time lots of P1 and few P2 messages can come. Sometimes lots of P2 messages with few P2 messages can come. Sometimes lots of P1 and P2 messages can come.
> In all these scenarios synapse should be able to guarantee the processing of P1 messages, even if it loose some P2 messages.
> To get this functionality in to ESB, we have implemented this feature in to synapse at two different levels. They are at HTTP transport level and mediation level.
> In the mediation level user can filter the messages using normal synapse capabilities for determining the priority and execute a sequence with a given priority.
> In the transport level there is a configuration to determine the priority from HTTP properties and execute the sequences accordingly.
> This feature is totally optional.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Commented: (SYNAPSE-608) Priority based mediation
Posted by "Ruwan Linton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12838380#action_12838380 ]
Ruwan Linton commented on SYNAPSE-608:
--------------------------------------
Supun, can you please provide the documentation and a sample as a patch??
Thanks,
Ruwan
> Priority based mediation
> ------------------------
>
> Key: SYNAPSE-608
> URL: https://issues.apache.org/jira/browse/SYNAPSE-608
> Project: Synapse
> Issue Type: New Feature
> Reporter: Supun Kamburugamuva
> Assignee: Ruwan Linton
> Attachments: priority-configuration.xml, Priority_Based_Mediation_Configuration.pdf, SYNAPSE-608.patch, synapse_sample_150.xml
>
>
> Priority based mediation allows users to execute sequences with a given priority. This is important when there is a high volume of traffic going through synapse which require different processing capabilities.
> First I'll explain the problem.
> Lets assume we have two types of messages coming in to the ESB. One type of message(P1) is very important and other type(P2) is not that important. User can afford to loose some of the P2 messages occasionally. Load characteristics of both messages change over time. Some time lots of P1 and few P2 messages can come. Sometimes lots of P2 messages with few P2 messages can come. Sometimes lots of P1 and P2 messages can come.
> In all these scenarios synapse should be able to guarantee the processing of P1 messages, even if it loose some P2 messages.
> To get this functionality in to ESB, we have implemented this feature in to synapse at two different levels. They are at HTTP transport level and mediation level.
> In the mediation level user can filter the messages using normal synapse capabilities for determining the priority and execute a sequence with a given priority.
> In the transport level there is a configuration to determine the priority from HTTP properties and execute the sequences accordingly.
> This feature is totally optional.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Updated: (SYNAPSE-608) Priority based mediation
Posted by "Supun Kamburugamuva (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Supun Kamburugamuva updated SYNAPSE-608:
----------------------------------------
Attachment: (was: SYNAPSE-608-Sample-documentation.patch)
> Priority based mediation
> ------------------------
>
> Key: SYNAPSE-608
> URL: https://issues.apache.org/jira/browse/SYNAPSE-608
> Project: Synapse
> Issue Type: New Feature
> Reporter: Supun Kamburugamuva
> Assignee: Ruwan Linton
> Attachments: priority-configuration.xml, Priority_Based_Mediation_Configuration.pdf, SYNAPSE-608-Sample-documentation.patch, SYNAPSE-608-samples.patch, SYNAPSE-608.patch, synapse_sample_150.xml
>
>
> Priority based mediation allows users to execute sequences with a given priority. This is important when there is a high volume of traffic going through synapse which require different processing capabilities.
> First I'll explain the problem.
> Lets assume we have two types of messages coming in to the ESB. One type of message(P1) is very important and other type(P2) is not that important. User can afford to loose some of the P2 messages occasionally. Load characteristics of both messages change over time. Some time lots of P1 and few P2 messages can come. Sometimes lots of P2 messages with few P2 messages can come. Sometimes lots of P1 and P2 messages can come.
> In all these scenarios synapse should be able to guarantee the processing of P1 messages, even if it loose some P2 messages.
> To get this functionality in to ESB, we have implemented this feature in to synapse at two different levels. They are at HTTP transport level and mediation level.
> In the mediation level user can filter the messages using normal synapse capabilities for determining the priority and execute a sequence with a given priority.
> In the transport level there is a configuration to determine the priority from HTTP properties and execute the sequences accordingly.
> This feature is totally optional.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Updated: (SYNAPSE-608) Priority based mediation
Posted by "Supun Kamburugamuva (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Supun Kamburugamuva updated SYNAPSE-608:
----------------------------------------
Attachment: SYNAPSE-608.patch
Attaching the patch.
> Priority based mediation
> ------------------------
>
> Key: SYNAPSE-608
> URL: https://issues.apache.org/jira/browse/SYNAPSE-608
> Project: Synapse
> Issue Type: New Feature
> Reporter: Supun Kamburugamuva
> Attachments: SYNAPSE-608.patch
>
>
> Priority based mediation allows users to execute sequences with a given priority. This is important when there is a high volume of traffic going through synapse which require different processing capabilities.
> First I'll explain the problem.
> Lets assume we have two types of messages coming in to the ESB. One type of message(P1) is very important and other type(P2) is not that important. User can afford to loose some of the P2 messages occasionally. Load characteristics of both messages change over time. Some time lots of P1 and few P2 messages can come. Sometimes lots of P2 messages with few P2 messages can come. Sometimes lots of P1 and P2 messages can come.
> In all these scenarios synapse should be able to guarantee the processing of P1 messages, even if it loose some P2 messages.
> To get this functionality in to ESB, we have implemented this feature in to synapse at two different levels. They are at HTTP transport level and mediation level.
> In the mediation level user can filter the messages using normal synapse capabilities for determining the priority and execute a sequence with a given priority.
> In the transport level there is a configuration to determine the priority from HTTP properties and execute the sequences accordingly.
> This feature is totally optional.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Updated: (SYNAPSE-608) Priority based mediation
Posted by "Supun Kamburugamuva (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Supun Kamburugamuva updated SYNAPSE-608:
----------------------------------------
Attachment: SYNAPSE-608.patch
Attaching a improved patch.
> Priority based mediation
> ------------------------
>
> Key: SYNAPSE-608
> URL: https://issues.apache.org/jira/browse/SYNAPSE-608
> Project: Synapse
> Issue Type: New Feature
> Reporter: Supun Kamburugamuva
> Attachments: SYNAPSE-608.patch
>
>
> Priority based mediation allows users to execute sequences with a given priority. This is important when there is a high volume of traffic going through synapse which require different processing capabilities.
> First I'll explain the problem.
> Lets assume we have two types of messages coming in to the ESB. One type of message(P1) is very important and other type(P2) is not that important. User can afford to loose some of the P2 messages occasionally. Load characteristics of both messages change over time. Some time lots of P1 and few P2 messages can come. Sometimes lots of P2 messages with few P2 messages can come. Sometimes lots of P1 and P2 messages can come.
> In all these scenarios synapse should be able to guarantee the processing of P1 messages, even if it loose some P2 messages.
> To get this functionality in to ESB, we have implemented this feature in to synapse at two different levels. They are at HTTP transport level and mediation level.
> In the mediation level user can filter the messages using normal synapse capabilities for determining the priority and execute a sequence with a given priority.
> In the transport level there is a configuration to determine the priority from HTTP properties and execute the sequences accordingly.
> This feature is totally optional.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Updated: (SYNAPSE-608) Priority based mediation
Posted by "Supun Kamburugamuva (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Supun Kamburugamuva updated SYNAPSE-608:
----------------------------------------
Attachment: SYNAPSE-608.patch
Re-attaching with improved documentation.
> Priority based mediation
> ------------------------
>
> Key: SYNAPSE-608
> URL: https://issues.apache.org/jira/browse/SYNAPSE-608
> Project: Synapse
> Issue Type: New Feature
> Reporter: Supun Kamburugamuva
> Attachments: SYNAPSE-608.patch
>
>
> Priority based mediation allows users to execute sequences with a given priority. This is important when there is a high volume of traffic going through synapse which require different processing capabilities.
> First I'll explain the problem.
> Lets assume we have two types of messages coming in to the ESB. One type of message(P1) is very important and other type(P2) is not that important. User can afford to loose some of the P2 messages occasionally. Load characteristics of both messages change over time. Some time lots of P1 and few P2 messages can come. Sometimes lots of P2 messages with few P2 messages can come. Sometimes lots of P1 and P2 messages can come.
> In all these scenarios synapse should be able to guarantee the processing of P1 messages, even if it loose some P2 messages.
> To get this functionality in to ESB, we have implemented this feature in to synapse at two different levels. They are at HTTP transport level and mediation level.
> In the mediation level user can filter the messages using normal synapse capabilities for determining the priority and execute a sequence with a given priority.
> In the transport level there is a configuration to determine the priority from HTTP properties and execute the sequences accordingly.
> This feature is totally optional.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Commented: (SYNAPSE-608) Priority based mediation
Posted by "Ruwan Linton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12832896#action_12832896 ]
Ruwan Linton commented on SYNAPSE-608:
--------------------------------------
Supun, can you attach a sample config file for the transport level priority based mediation, and a synapse config which works with the priority based mediation.
Thanks,
Ruwan
> Priority based mediation
> ------------------------
>
> Key: SYNAPSE-608
> URL: https://issues.apache.org/jira/browse/SYNAPSE-608
> Project: Synapse
> Issue Type: New Feature
> Reporter: Supun Kamburugamuva
> Assignee: Ruwan Linton
> Attachments: SYNAPSE-608.patch
>
>
> Priority based mediation allows users to execute sequences with a given priority. This is important when there is a high volume of traffic going through synapse which require different processing capabilities.
> First I'll explain the problem.
> Lets assume we have two types of messages coming in to the ESB. One type of message(P1) is very important and other type(P2) is not that important. User can afford to loose some of the P2 messages occasionally. Load characteristics of both messages change over time. Some time lots of P1 and few P2 messages can come. Sometimes lots of P2 messages with few P2 messages can come. Sometimes lots of P1 and P2 messages can come.
> In all these scenarios synapse should be able to guarantee the processing of P1 messages, even if it loose some P2 messages.
> To get this functionality in to ESB, we have implemented this feature in to synapse at two different levels. They are at HTTP transport level and mediation level.
> In the mediation level user can filter the messages using normal synapse capabilities for determining the priority and execute a sequence with a given priority.
> In the transport level there is a configuration to determine the priority from HTTP properties and execute the sequences accordingly.
> This feature is totally optional.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Updated: (SYNAPSE-608) Priority based mediation
Posted by "Supun Kamburugamuva (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Supun Kamburugamuva updated SYNAPSE-608:
----------------------------------------
Attachment: (was: SYNAPSE-608.patch)
> Priority based mediation
> ------------------------
>
> Key: SYNAPSE-608
> URL: https://issues.apache.org/jira/browse/SYNAPSE-608
> Project: Synapse
> Issue Type: New Feature
> Reporter: Supun Kamburugamuva
>
> Priority based mediation allows users to execute sequences with a given priority. This is important when there is a high volume of traffic going through synapse which require different processing capabilities.
> First I'll explain the problem.
> Lets assume we have two types of messages coming in to the ESB. One type of message(P1) is very important and other type(P2) is not that important. User can afford to loose some of the P2 messages occasionally. Load characteristics of both messages change over time. Some time lots of P1 and few P2 messages can come. Sometimes lots of P2 messages with few P2 messages can come. Sometimes lots of P1 and P2 messages can come.
> In all these scenarios synapse should be able to guarantee the processing of P1 messages, even if it loose some P2 messages.
> To get this functionality in to ESB, we have implemented this feature in to synapse at two different levels. They are at HTTP transport level and mediation level.
> In the mediation level user can filter the messages using normal synapse capabilities for determining the priority and execute a sequence with a given priority.
> In the transport level there is a configuration to determine the priority from HTTP properties and execute the sequences accordingly.
> This feature is totally optional.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Updated: (SYNAPSE-608) Priority based mediation
Posted by "Supun Kamburugamuva (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Supun Kamburugamuva updated SYNAPSE-608:
----------------------------------------
Attachment: SYNAPSE-608-Sample-documentation.patch
SYNAPSE-608-samples.patch
Attaching 2 samples and documentation.
Thanks,
Supun..
> Priority based mediation
> ------------------------
>
> Key: SYNAPSE-608
> URL: https://issues.apache.org/jira/browse/SYNAPSE-608
> Project: Synapse
> Issue Type: New Feature
> Reporter: Supun Kamburugamuva
> Assignee: Ruwan Linton
> Attachments: priority-configuration.xml, Priority_Based_Mediation_Configuration.pdf, SYNAPSE-608-Sample-documentation.patch, SYNAPSE-608-samples.patch, SYNAPSE-608.patch, synapse_sample_150.xml
>
>
> Priority based mediation allows users to execute sequences with a given priority. This is important when there is a high volume of traffic going through synapse which require different processing capabilities.
> First I'll explain the problem.
> Lets assume we have two types of messages coming in to the ESB. One type of message(P1) is very important and other type(P2) is not that important. User can afford to loose some of the P2 messages occasionally. Load characteristics of both messages change over time. Some time lots of P1 and few P2 messages can come. Sometimes lots of P2 messages with few P2 messages can come. Sometimes lots of P1 and P2 messages can come.
> In all these scenarios synapse should be able to guarantee the processing of P1 messages, even if it loose some P2 messages.
> To get this functionality in to ESB, we have implemented this feature in to synapse at two different levels. They are at HTTP transport level and mediation level.
> In the mediation level user can filter the messages using normal synapse capabilities for determining the priority and execute a sequence with a given priority.
> In the transport level there is a configuration to determine the priority from HTTP properties and execute the sequences accordingly.
> This feature is totally optional.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Commented: (SYNAPSE-608) Priority based mediation
Posted by "Ruwan Linton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12832901#action_12832901 ]
Ruwan Linton commented on SYNAPSE-608:
--------------------------------------
Supun,
We should be able to use this for all the transports, if not all most of them should implement this, there fore I am moving out the evaluators package out from the nhttp transport module.
I am planning to do few other refactoring as well, but lets commit the code and do them as the secondary step.
Thanks,
Ruwan
> Priority based mediation
> ------------------------
>
> Key: SYNAPSE-608
> URL: https://issues.apache.org/jira/browse/SYNAPSE-608
> Project: Synapse
> Issue Type: New Feature
> Reporter: Supun Kamburugamuva
> Assignee: Ruwan Linton
> Attachments: SYNAPSE-608.patch
>
>
> Priority based mediation allows users to execute sequences with a given priority. This is important when there is a high volume of traffic going through synapse which require different processing capabilities.
> First I'll explain the problem.
> Lets assume we have two types of messages coming in to the ESB. One type of message(P1) is very important and other type(P2) is not that important. User can afford to loose some of the P2 messages occasionally. Load characteristics of both messages change over time. Some time lots of P1 and few P2 messages can come. Sometimes lots of P2 messages with few P2 messages can come. Sometimes lots of P1 and P2 messages can come.
> In all these scenarios synapse should be able to guarantee the processing of P1 messages, even if it loose some P2 messages.
> To get this functionality in to ESB, we have implemented this feature in to synapse at two different levels. They are at HTTP transport level and mediation level.
> In the mediation level user can filter the messages using normal synapse capabilities for determining the priority and execute a sequence with a given priority.
> In the transport level there is a configuration to determine the priority from HTTP properties and execute the sequences accordingly.
> This feature is totally optional.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org