Hi Rushmin, According to the nhttp architecture it uses two buffers for request read(Input Stream) and request write to BE(output stream). But those two buffers has raw byte stream.But in the mediation layer requests are represent as OMElements.So InputStream is need to convert OMElement and again to OutputStream so that is handle by Axis2 Level message builders and formatters. Message builders create OMElement from input stream and formatters again serialized it. So before moving to mediation layer messages are converted to OMElement but this not fully build of the message this is only partially build because it uses Steaming API (Stax parser) how ever it has significant build overhead comparing to raw byte stream.
If mediators are content aware then message is actually fully read to the memory by Streaming API. But if you used binary relay in nhttp transport then messages are processed as byte streams with out partially or fully building of the message.But it can not be used with content aware mediators. thanks IsuruR On Thu, Oct 23, 2014 at 9:30 PM, Rushmin Fernando <[email protected]> wrote: > Does the framework build the message before it submits a message for > mediation to a content aware mediator > > or > > does it build the message upfront if there is a content mediator in > possible sequence paths ? > > Thanks > Rushmin > > > > -- > *Rushmin Fernando* > *Technical Lead* > > WSO2 Inc. <http://wso2.com/> - Lean . Enterprise . Middleware > > email : [email protected] > mobile : +94772310855 > > > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Best Regards Isuru Ranawaka M: +94714629880 Blog : http://isurur.blogspot.com/
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
