[
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-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org
