Serge Knystautas-2 wrote:
> 
> 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.
> 

Could anybody please be so kind and start with an explanation what
"streaming", or "non-streaming" means? I have the definite impression, that
we are talking quite different things here. In particular, I am far from
understanding why they should be mutually exclusive.

Jochen

-- 
View this message in context: 
http://www.nabble.com/-Mime4J--Support-For-Non-Streaming-Inputs-tf4490104.html#a12829975
Sent from the James - Dev mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to