Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
Received-SPF: pass (asf.osuosl.org: domain of davanum@gmail.com designates
 64.233.170.202 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=A0j74umcdwpqQBQjjq5pX1UJtsqbGBr4WnFbTrorvXyZKMtMAkKTNaJOd/55wx8pvJdhjneUAGOeszY8hMVeIw51xIyTXhors40Y8B2wk0aDwnmlAWcVn6DoUY2RqaJdL0GBHa6iEF1xUOoJTptMV8F+zTxJCgnxnJb98emjCXI=
Message-ID: <19e0530f050718084142b76733@mail.gmail.com>
Date: Mon, 18 Jul 2005 11:41:07 -0400
From: Davanum Srinivas <davanum@gmail.com>
Reply-To: dims@apache.org
To: axis-dev@ws.apache.org
Subject: Re: [Axis2] MIME Content ID handling for MTOM
Cc: Thilina Gunarathne <csethil@gmail.com>
In-Reply-To: <1121699572.14130.65.camel@localhost.localdomain>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <e9115cfd050715075977ded09c@mail.gmail.com>
	 <19e0530f050715080625dc6f91@mail.gmail.com>
	 <19e0530f0507151959b6c95ba@mail.gmail.com>
	 <e9115cfd05071802076583dfcf@mail.gmail.com>
	 <e9115cfd05071802204a5140eb@mail.gmail.com>
	 <19e0530f050718032729c227fe@mail.gmail.com>
	 <1121699572.14130.65.camel@localhost.localdomain>

Sanjiva,

On 7/18/05, Sanjiva Weerawarana <sanjiva@opensource.lk> wrote:
> On Mon, 2005-07-18 at 06:27 -0400, Davanum Srinivas wrote:
> > Thilina,
> >
> > i'd suggest you concentrate on cleaning up the code for MTOM and
> > writing more test cases with actual assert statements while we
> > research this a bit more.
>=20
> You do agree with the principle of getting the faulty impl corrected,
> right?

if we determine that it is faulty. then yes. let's not change it for now.

> > for example
> > - there are so many while loops which don't check if there are any
> > more characters in the stream
> > - are u handling unsupposted media exception? are we throwing it. are
> > we catching it? are we handling all the exceptions in the specs? are
> > there test cases for it?
> > - are we handling all the http status codes specified in mtom/xop specs=
?
> > - why are we createing intermediate ByteArrayOutputstreams and putting
> > things in them. what is going to happen if we get 1 GB attachment or
> > 512 MB soap part? there should not be any intermediate storage
> > especially of things that are likely to grow.
>=20
> +1 for cleaning up the code.
>=20
> > - was there any effort to at least architect the code so that we can
> > add mime and SwA later when we get a chance?
>=20
> A XOP message is supposed to be wire-compatible with SwA. Is that not
> the case?
>=20
> What did you mean by "mime"?

typo i meant dime

> > - Can we get rid of httptransportsender as we talked about earlier?
> > and so on....
>=20
> Not directly MTOM related .. in progress but slow week this week because
> Ajith, Chathura and Eran are all at AC Europe.
>=20
> Sanjiva.
>=20
>=20
>=20


--=20
Davanum Srinivas -http://blogs.cocoondev.org/dims/