On Fri, 2008-07-04 at 00:51 -0400, Sahan Gamage wrote:
> Manjula,
>
> How about HTTP 1.0 case ? I think we should still support HTTP 1.0 and
> it does not support chunking IIRC. Also what happens in SMTP case
> (once/if we have it in place) ? I think MTOM implementation should be
> somewhat (not
On Fri, Jul 4, 2008 at 10:21 AM, Sahan Gamage <[EMAIL PROTECTED]> wrote:
> Manjula,
>
> How about HTTP 1.0 case ? I think we should still support HTTP 1.0 and
> it does not support chunking IIRC. Also what happens in SMTP case
> (once/if we have it in place) ?
SMTP transport binding for SOAP1.1
Manjula,
How about HTTP 1.0 case ? I think we should still support HTTP 1.0 and
it does not support chunking IIRC. Also what happens in SMTP case
(once/if we have it in place) ? I think MTOM implementation should be
somewhat (not completely) transport independent and if the underlying
transport su
On Fri, 2008-07-04 at 06:40 +0530, Danushka Menikkumbura wrote:
> >
> The MTOM spec does not say anything about data compression right?.
> Otherwise we could have achieved even better performance with compression.
Yes the MTOM spec does not say anything about compression. So even we
compress the
Hi,
I was able to fix MTOM caching stuff for both sender and receiving ends.
In sender side instead of loading the whole attachment it will send the
attachment + data as chunked. Only very small portion of the attachment
will be loaded in to the memory at any given time. In order to achieve
thi
Manjula Peiris wrote:
Hi,
I was able to fix MTOM caching stuff for both sender and receiving ends.
In sender side instead of loading the whole attachment it will send the
attachment + data as chunked. Only very small portion of the attachment
will be loaded in to the memory at any given time. In
Hi,
I was able to fix MTOM caching stuff for both sender and receiving ends.
In sender side instead of loading the whole attachment it will send the
attachment + data as chunked. Only very small portion of the attachment
will be loaded in to the memory at any given time. In order to achieve
this I