Still chewing on the first part of your message, but the last question I can have a crack at now…
Why doesn’t groov support rtsp streaming?
As mentioned in my blog about the groov Camera Gadget, (and [URL=“http://www.opto22.com/community/showthread.php?t=1208”]in another thread in here) the camera gadget is just a place holder for the camera image. groov does not do any decoding, it just displays the jpg from the camera at the nominated refresh rate.
Why just a place holder for an image?
Because the actual camera stream decoding needs to be handled by the browser, not groov.
Ok, so why don’t we do it?
Because of browser incompatibility.
Here is a nice post of one users experience on stackoverflow.
And another. (Take a moment to read the many suggestions).
Here is a nice overview from the Firefox devs. (Note their closing comment in the RTSP section “Using RTP with RTCP allows for adaptive streaming. This is not yet supported natively in most browsers”)
Keep in mind that we need ‘the solution’ to work not only on PC, Mac and Linux desktops, but also iOS, Android, and Windows mobile devices.
Long answer short. We looked at it. We tried it. We implemented the best solution for now.
We have not closed the case, our engineers check in frequently to see the state of play. As soon as there is a solution that supports the browsers and platforms that users use, we will be all over it.