Re: [reSIProcate] multipart mime

[Byron Campen <bcampen@xxxxxxxxxxxx>]

	I just found a bug in MultipartMixedContents that occurs when you  
copy construct from an unparsed MultipartMixed (the call to parts()  
was causing the original to become parsed after we had initialized  
the LazyParser as _unparsed_, and putting the parsed bits into our  
mContents vector, meaning that when we did parse, another copy of  
everything was put in mContents.) I'll have a fix ready momentarily.

Best regards,
Byron Campen

> I found a puzzling note in my email from late 2006 indicating that I
> thought that multipart mime in resip was not working. Does anybody
> remember anything about this? Is anybody using this or has tested it?
> I am guessing that the problems are in the dum library and not in the
> lower levels but not sure.
>
> Thanks
> Jason
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel@xxxxxxxxxxxxxxx
> https://list.resiprocate.org/mailman/listinfo/resiprocate-devel

Attachment: smime.p7s
Description: S/MIME cryptographic signature