synapse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Supun Kamburugamuva (JIRA)" <>
Subject [jira] Updated: (SYNAPSE-608) Priority based mediation
Date Fri, 12 Feb 2010 09:26:27 GMT


Supun Kamburugamuva updated SYNAPSE-608:

    Attachment: Priority_Based_Mediation_Configuration.pdf

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.


> Priority based mediation
> ------------------------
>                 Key: SYNAPSE-608
>                 URL:
>             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:
For additional commands, e-mail:

View raw message