Mailing-List: contact dev-help@synapse.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@synapse.apache.org
Received-SPF: pass (athena.apache.org: domain of indika.kuma@gmail.com
 designates 72.14.246.240 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version
         :content-type:references;
        b=urAnjfRGlkf2/3fnE6qt123AUI2D2THVJHSxmQXahbz71obYkqBObvp4//SPoq7gud
         M3JOcIG32qkaa5StPcd6/nt+56AeoJCccy5MIBVCDR7YKlVknQL37t1j8gWcxryN4V5t
         3xBiUxLX9sS5+7/giUjgoPByJP5PNPj7eZY7k=
Message-ID: <d173c15d0806270043n71267449w2859821454a3e027@mail.gmail.com>
Date: Fri, 27 Jun 2008 13:13:28 +0530
From: "indika kumara" <indika.kuma@gmail.com>
To: dev@synapse.apache.org
Subject: Re: Improving performance even more :)
In-Reply-To: <672a01200806260921k4c9a6783lc858df24c8e25c2@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_12697_2047213.1214552608944"
References: <88f5d710806250743p63239218tc672bb5c882c5132@mail.gmail.com>
	 <672a01200806260728k2de80b59y210bc9637705b05@mail.gmail.com>
	 <88f5d710806260741u79ddf529u7aba815078a932fc@mail.gmail.com>
	 <672a01200806260921k4c9a6783lc858df24c8e25c2@mail.gmail.com>

------=_Part_12697_2047213.1214552608944
Content-Type: text/plain; charset=WINDOWS-1252
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hi All

Some thought...

Currently message building and serializing is in transport layer. According
to the content type ,message is being built and we cannot control the
building process. For example , if the content type is corresponding to the
SOAP , then SOAP message is built and we cannot avoid it. This is fine only
if we use or access SOAP message. But if we can dispatch to
synapse,proxyservices,etc without touching SOAP message and if we will not
touch the SOAP message within synapse, then , we should not want a SOAP
message. But , currently , we have not that control .

If we can provide a option to transport to specify whether to build a
message or not (build and set as SOAP envelope ) and also if can provide a
way in synapse language to specify whether to build a message or not(Build
mediator which builds message and sets as SOAP envelope =96 default behavio=
r
may use content-type, but we have to have options to override it.). One
other possibility is , with in transport layer , the message always set as
stream or OMDatasource (use BinaryBuilder ) irrespective of content type an=
d
whenever try to access message on the first time
(messagecontext.getSOAPEnvelope()) and if SOAP envelope has not been built
yet, then builds it and sets as Envelope. This will be completely avoid
building message as a SOAP envelope , if we have not any interest in it.

For serialization part , we can do the same thing.

I don't know this is a good suggestion , but I believe , for scenarios, tha=
t
we don't access SOPA message, we have to completely avoid building it.

Thanks
Indika

------=_Part_12697_2047213.1214552608944
Content-Type: text/html; charset=WINDOWS-1252
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline


=09<meta http-equiv=3D"CONTENT-TYPE" content=3D"text/html; charset=3Dutf-8"=
><title></title><meta name=3D"GENERATOR" content=3D"OpenOffice.org 2.3  (Li=
nux)">
=09
=09
=09<style type=3D"text/css">
=09&lt;!--
=09=09@page { size: 215.9mm 279.4mm; margin: 20mm }
=09=09P { margin-bottom: 2.12mm }
=09--&gt;
=09</style>


<p style=3D"margin-bottom: 0mm;" align=3D"justify"><font face=3D"Times, ser=
if">Hi All </font><br>
</p>
<p style=3D"margin-bottom: 0mm;" align=3D"justify"><font face=3D"Times, ser=
if">Some
thought... </font>
</p>

<p style=3D"margin-bottom: 0mm;" align=3D"justify"><font face=3D"Times, ser=
if">Currently
message building and serializing is in transport layer. According to
the content type ,message is being built and we cannot control
the building process. For example , if the content type is corresponding
to the SOAP , then SOAP message is built and we cannot avoid it. This
is fine only if we use or access  SOAP message. But if we can
dispatch to synapse,proxyservices,etc without touching SOAP message
and if we will not touch the SOAP message within synapse, then , we
should not want a SOAP message. But , currently , we have not that
control .</font><br>
</p>

<p style=3D"margin-bottom: 0mm;" align=3D"justify"><a name=3D"DDE_LINK"></a=
><font face=3D"Times, serif">If
we can provide a option to transport to specify whether to build a
message or not (build and set as SOAP envelope ) and also if can
provide a way in synapse language to specify whether to build a
message or not(Build mediator which builds message and sets as SOAP
envelope =96 default behavior may use content-type, but we have to
have options to override it.). One other possibility is , with in
transport layer , the message always set as stream or OMDatasource
(use BinaryBuilder ) irrespective of content type and whenever try to
access message on the first time (messagecontext.getSOAPEnvelope())
and if SOAP envelope has not been built yet, then builds it and sets
as Envelope. This will be completely avoid building message as a SOAP
envelope , if we have not any interest in it.</font><br>
</p>
<p style=3D"margin-bottom: 0mm;" align=3D"justify"><font face=3D"Times, ser=
if">For
serialization part , we can do the same thing. </font>
</p>


<p style=3D"margin-bottom: 0mm;" align=3D"justify"><font face=3D"Times, ser=
if">I
don&#39;t know this is a good suggestion , but I believe , for scenarios,
that we don&#39;t access SOPA message, we have to completely avoid
building it.</font><br>
</p>

<p style=3D"margin-bottom: 0mm;" align=3D"justify"><font face=3D"Times, ser=
if">Thanks<br>Indika</font></p>

------=_Part_12697_2047213.1214552608944--