On Sun, Mar 9, 2008 at 4:05 PM, Jukka Zitting <[EMAIL PROTECTED]> wrote: > Hi, > > > On Sun, Mar 9, 2008 at 11:53 AM, Robert Burrell Donkin > <[EMAIL PROTECTED]> wrote: > > On Sun, Mar 9, 2008 at 9:41 AM, Jukka Zitting <[EMAIL PROTECTED]> wrote: > > > > A search feature is typically only useful when applied to a collection > > > of messages, so I'm not sure if something like that really makes sense > > > in the scope of Mime4J. > > > > the object i had in mind performs a character search of the bodies and > > fields of one MIME document. this isn't a byte-wise but > > character-based search which requires decoding of transfer encodings > > and setting appropriate charsets. the function isn't complex but > > getting the decoding right for each part is a little fiddly and > > requires an understanding of MIME encoding. > > Isn't most of that complexity already be handled by the new getReader() > method?
yes it is. it's just a classic pull parsing implementation. so maybe it would work better in the documentation as a worked example... - robert --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
