> From: Koen Deforche [mailto:[EMAIL PROTECTED] > Sent: 18. november 2008 16:18 > Instead, an asynchronous way of doing would be in pseudo code: > > void streamNextPart() { > if (resource.hasMoreData()) { > // .. get next data chunk > ... > > // send to browser, and supply a callback to be called when done > sendAsyncToBrowser(..., &streamNextPart); > } > } > > The latter approach has the benefit of being entirely > scalable in all situations, but is more complicated, and for > an embedded platform this scalability (towards many > concurrent threads) is not an immediate concern. > > Both solutions solve your problem, imho, and so we will pick one.
Sounds good. Can you say anything about when you plan to implement it? I'm considering workarounds, e.g. adding another http server which can stream incrementally, but I will not spend much time on that, if you plan to implement streaming using multiple chunks soon. -- Med venlig hilsen / Best regards Michael Sørensen Loft, Mjølner Informatics A/S ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ witty-interest mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/witty-interest
