the code in question will strip the '<' and '>' from content-id in the mime part and then add it to the internal collection of parts.
Question is IF the '<'/'>' is absent then should we throw an error or not. Thilina, BTW, i saw another problem. if i see the whitemesa traces (http://www.whitemesa.net/mtom-cr-traces/mtom-cr-2a-resp.txt) in the xml part they use: <xop:Include href="cid:uuid:3C689526-B778-4059-B0C6-0D01120167B8"; /> and in the mimepart they use: Content-Id: <uuid:3C689526-B778-4059-B0C6-0D01120167B8> note that cid: is not present in the mimepart. according to the RFC, is this incorrect? -- dims On 7/19/05, Davanum Srinivas <[EMAIL PROTECTED]> wrote: > Let him at least write the code and then you can -1 it. what's gotten > into you? :) > > -- dims > > On 7/19/05, Sanjiva Weerawarana <[EMAIL PROTECTED]> wrote: > > An ENTIRE line of bug-compatible code?? Oh my god, how terrible! Hell > > no, definite -1 on that one!!!! > > > > Sanjiva. > > > > On Tue, 2005-07-19 at 10:31 -0400, Davanum Srinivas wrote: > > > it's a one line change!!! > > > > > > On 7/19/05, Sanjiva Weerawarana <[EMAIL PROTECTED]> wrote: > > > > On Tue, 2005-07-19 at 07:44 -0400, Davanum Srinivas wrote: > > > > > Can we do this? let's try to be accomodating to what we accept (means > > > > > accept messages with or without '<' and '>') but generate messages > > > > > according to the RFC? At least till we get confirmation from the folks > > > > > researching the problem? > > > > > > > > Um .. temporary bug compat mode? I'd rather just let it be until we get > > > > feedback from the MSFT guys .. I'm sure they'll report back soon saying > > > > "yes its a bug we'll fix it" and then we can do the right thing. Once > > > > you start putting these "conveniences" it becomes hard to remove 'em .. > > > > > > > > Sanjiva. > > > > > > > > > > > > > > > > > > > > > > > > > -- > Davanum Srinivas -http://blogs.cocoondev.org/dims/ > -- Davanum Srinivas -http://blogs.cocoondev.org/dims/
