Hi Folks,

Just to briefly explain how other messaging scenarios are made to work with
the relay:

1. A special handler checks whether security or some other content aware
module is engaged on the target service and builds the messages if
necessary.
2. Each mediator knows whether they should build the message or not
(depending on their configuration). If necessary, mediators will build the
message.

As a result a sequence such as the following will run in the pure pass
through mode:

<sequence>
    <log/>
    <send/>
</sequence>

Something like the following will cause the message to be built at the log
mediator:

<sequence>
   <log level="full"/>
   <send/>
</sequence>

In the following proxy service, the in-sequence will be in the pass through
mode. The out-sequence will build the message at the xslt mediator:

<proxy name="foo">
   <target endpoint="bar">
      <inSequence>
          <log/>
      </inSequence>
      <outSequence>
          <log/>
          <xslt key="baz"/>
          <send/>
      </outSequence>
   </target>
</proxy>

Thanks,
Hiranya

On Tue, Apr 17, 2012 at 9:32 AM, indika kumara <indika.k...@gmail.com>wrote:

> +1 great donation!  Would love to see the support for any mediation
> scenario with it too.
>
> Regards,
>
> Indika
>
>
> On Mon, Apr 16, 2012 at 4:17 PM, Hiranya Jayathilaka <hiranya...@gmail.com
> > wrote:
>
>> Hi Folks,
>>
>> Message relay is a performance enhancer we have developed for WSO2 ESB.
>> We are now thinking about contributing this code to Synapse. There are two
>> main components for this:
>>
>> 1. A builder-formatter pair for mediating messages without building the
>> Axiom infoset
>> 2. A new HTTP transport (pass through transport)
>>
>> These can be used independently of each other. One of the existing
>> limitations of this code is that it restricts the scenarios that we can run
>> on Synapse to pass through scenarios. But I've been working on making this
>> code work with any mediation scenario (transformation, security etc). So
>> that way we will be able to run Synapse with these optimizers by default
>> and still all the messaging scenarios would work out of the box.
>>
>> A performance comparison of the current NHTTP transport and the above
>> optimizers can be found at [1].
>>
>> Appreciate your feedback on this.
>>
>> Thanks,
>> Hiranya
>>
>> [1] -
>> http://wso2.org/library/articles/2012/03/performance-benchmarking-wso2-esb-different-message-transfer-mechanisms
>>
>> --
>> Hiranya Jayathilaka
>> Associate Technical Lead;
>> WSO2 Inc.;  http://wso2.org
>> E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
>> Blog: http://techfeast-hiranya.blogspot.com
>>
>
>


-- 
Hiranya Jayathilaka
Associate Technical Lead;
WSO2 Inc.;  http://wso2.org
E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
Blog: http://techfeast-hiranya.blogspot.com

Reply via email to