A Q. re: upcoming CRM114 library...

Eugene Crosser <[email protected]> Tue, 09 Mar 2010 16:20:56 +0300
Newsgroups gmane.mail.spam.crm114
Message-ID <[email protected]>
Bill,

a quick question: will the upcoming library support feeding data
chunk-by-chunk or would it require the complete document to be mapped
into memory?

This is why I ask:
imagine a deeply-nested MIME message, that contains different text body
parts in different encodings, parts with different binary data, possibly
MIME-encoded in different ways (b64 and q-p), possibly residing in
different "message/rfc822" parts at different depths. While I
recursively parse this MIME structure, at any time I have a single
fully-decoded (and possibly charset-translated) body part with its
associated set of headers. But, I usually have no reason to reconstruct
the complete message from these decoded/translated parts (and it would
even be a wrong thing to do, from classification perspective). I'd
rather pass the freshly obtained/decoded chunk of the message to the
classifier along with the opaque "state structure", and instantly forget
about it, and continue traversal of the message tree. When I am over,
I'll ask the "state structure" about the result of classification
(/learning).

Will such thing be possible with the new library?

Thanks,

Eugene

------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev

_______________________________________________
Crm114-general mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/crm114-general
signature.asc (application/pgp-signature, 261 B)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkuWSzsACgkQfrw/cIw6UWkMZACeJU8DLQktoiuHx1DwAf+GzSd9
feEAn25bmrIvCeIZYaGs1ztgXfxXGx0v
=I4tX
-----END PGP SIGNATURE-----