Am 26.01.2014 13:06, schrieb Carsten A. Arnholm: ... >> Using chunked encoding might be an interesting feature for tntnet. A >> component should be able to call "reply.setChunkedEncoding()", in which >> case the component is not allowed to fail any more but can send data >> synchronously to the client. Any opinions? > If that is required, no problem. > > I have source code to capture images from the PI camera now. What could > be interesting is to make a tntnet demo with live streaming. I think it > could be interesting to a lot of PI enthusiasts and a great way to > promote tntnet as well. > > Carsten > I don't really know, if it is required. It just reasonable. When capturing a video stream from the camera, the application can't know, how large the video stream will be without capturing the whole video and look, how many bytes it contains. So tntnet normally capture the stream in a std::ostringstream.
I already implemented yesterday and today chunked encoding with tntnet. It works quite fine. I have to fix a crash on cleanup but when it is done, I will commit it. I think, it is a nice feature. Tommi ------------------------------------------------------------------------------ CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk _______________________________________________ Tntnet-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tntnet-general
