On 9/20/07, Robert Burrell Donkin <[EMAIL PROTECTED]> wrote: > i'd like to gauge opinions about whether anyone else feels strongly > about supporting non-streaming inputs for MimeTokenStream. i've been > keeping this in mind whilst reviewing jochen's patches but this has > lead to conflicts about the design > (https://issues.apache.org/jira/browse/MIME4J-30). the price of > support will be greater complexity.
Thanks for raising this project scope issue since IMHO these are the bigger than technical decisions. If I can restate, currently we support both non-streaming and streaming uses, and have a cursor API out of that. The project scope question at hand is if we drop support for non-streaming (and thus the cursor API) and just optimize for the streaming use case. Is that right? And if so, can you give me a use case or two for non-streaming? -- Serge Knystautas Lokitech >> software . strategy . design >> http://www.lokitech.com p. 301.656.5501 e. [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
