Hi Tommy, Thanks for replying....
On 25. jan. 2014 21:55, Tommi Mäkitalo wrote: > there is a project named vdr, which implements a video disk recorder > based on linux. And there is a web front end as a plugin available, > which runs on tntnet: http://www.vdr-wiki.de/wiki/index.php/Live-plugin. > They stream videos via tntnet. It is more a download of videos, which > are then showed in the browser. But it works. Ok, that is kind of interesting. Maybe it isn't too different, but I was thinking first of all of direct viewing of live preview data from a camera such as the raspberry PI camera, for example showing current weather. But viewing something pre-recorded is also interesting. Btw, I put a test video captured with the Raspberry PI camera at http://arnholm.org/tmp/raspberry_pi_snow_c.mp4 It is just 10 seconds captured at 20 fps showing snow falling. It is best viewed by downloading to the HD and viewed with e.g. Dragon Player (Ubuntu) or Media Player (Windows). I can view live previews like this over the local network using 'netcat', and it would be nice to show similar live on the web using tntnet. > One problem they encountered was the watchdog feature of tntnet. Tntnet > expects, that a component returns within 10 minutes. If it does not, > tntnet restarts itself for safety reasons, because tntnet thinks the > component is in a endless loop. The solution is calling > "request.touch()" regularly to tell tntnet, that the component is still > working. Ok, that sounds resonable. > Another problem, which happens in case the video is actually a stream > is, that tntnet needs the content size before it starts sending the > stream. The content size is needed since it is part of the http header. Under normal circumstances, this should be known beforehand, i.e. it could be something the tntnet application told tntnet. I have written video capture applicatons before (for astronomy use), and we often know the pixel resolution and number of cols/rows. > 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 ------------------------------------------------------------------------------ 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
