--- Sanjiva Weerawarana <[EMAIL PROTECTED]> wrote:
> Defer until F2F discussion on the right arch for
> MTOM support?
> The last time we had the discussion on the list IIRC
> there were
> multiple proposals .. but now we have at least one
> concrete
> realization.
> 
> In any case, seems to me we should put up Thilina
> for committer?

+1 for voting in Thilina as a committer. IMO there
weren't any counter arguments to Thilina's
proposal+impl. Thilina has also got test cases to
backup his code and he is now focusing on interop
testing as well.

I would also like to propose that we do a complete
review of OM interfaces and there implementations
since quite a few things have now been integrated and
patched up to it since its first design. 

--Dasarath
> 
> Sanjiva.
> 
> ----- Original Message ----- 
> From: "Ajith Ranabahu" <[EMAIL PROTECTED]>
> To: <[email protected]>; <[EMAIL PROTECTED]>
> Sent: Tuesday, March 15, 2005 7:07 PM
> Subject: Re: [Axis2] MTOM Patch
> 
> 
> > Hi dims,
> > Well I don't think we should commit MTOM stuff
> directly into the main
> > area. Since we have not yet agreed officially on
> any MTOM
> > representation mechanism, my guess is we should
> keep it in the scratch
> > area for the time being.
> > (Actually that is why we did not commit it in the
> main area in the
> > first place :))
> >
> >
> > On Tue, 15 Mar 2005 08:01:35 -0500, Davanum
> Srinivas <[EMAIL PROTECTED]>
> wrote:
> > > can someone integrate the mtom stuff into the
> main area?
> > >
> > > -- dims
> > >
> > > On Tue, 15 Mar 2005 16:54:15 +0600, Thilina
> Gunarathne
> > > <[EMAIL PROTECTED]> wrote:
> > > > Hi,
> > > >
> > > > Please apply the patch to scratch/thilina/mtom
> folder.
> > > >
> > > > Thanks,
> > > > Thilina.
> > > >
> > > >
> > > >
> > >
> > > --
> > > Davanum Srinivas -
> http://webservices.apache.org/~dims/
> > >
> >
> >
> > -- 
> > Ajith Ranabahu
> >
> 
> 


                
__________________________________ 
Do you Yahoo!? 
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/ 

Reply via email to