Re: [evolution-patches] 47824, multipart messages re-using teh same boundary



On Wed, 2005-01-12 at 15:59 -0500, Jeffrey Stedfast wrote:
looks good... but:

+       while ((state = camel_mime_parser_step(cmp, &buf, &len)) !=
CAMEL_MIME_PARSER_STATE_MULTIPART_END) {

what happens here if we get EOS for example? will things work out ok?

Yes.  The parser enforces a particular state sequence even with truncated data or a disconnected stream.  This is exactly the same sequence as is used in camel-multipart.c:construct_from_parser already.

--
Michael Zucchi <notzed ximian com>
"Ride, Work, Sleep. Beer."
Novell's Evolution and Free Software Developer


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]