Re: MIME multipart/related

Benjamin Sonntag <[email protected]> writes:

> rr_frame_mime_get_body          (RRFrame *frame);
> rr_frame_mime_get_body_size     (RRFrame *frame);
> 
> Just a small question : it seems that the two functions above cannot deal
> with multipart/related complex mime messages isn't it ? 
> 
> Can you tell me if I am wrong, if I'm right, I will use libgmime ...

Hi Ben,

Yes, that's quite right that the MIME 'handling' functions are quite inadequate
at the moment. The two you mention are basically there just to find the end of
the headers to access the main message body easily.
And as you've noted it doesn't handle multi-part messages well.

Whereas it's certainly possible to use a complex/complete MIME handling
library within a profile, it's probably overkill for use within the BEEP core
library itself (as Jonas pointed out). 

I think we should have a simple set of functions to be able to:

 * Parse headers and access values

 * Handle multipart correctly and well

I haven't thought much about it yet, but I was thinking something along the
lines of a function to traverse available parts or get a list of them, then
leave the rest of the processing to the profile.

What do you guys think of that idea? 

/D

-- 
Daniel Lundin  | [email protected]
CodeFactory AB | http://www.codefactory.se/