I am experimenting with WebRTC video chat and wish to extend that work to the RPi2 but have not determined how to implement so as to activate video acceleration. There are references to uv4l but I have not seen anything specific on if and how one can set up the RPi2 to run WebRTC in a browser with video acceleration.
It seems mate may be a good base and can run chromium but would appreciate guidance in if and how I can turn on video acceleration in such a mate/chromium WebRTC (HTML5 ) situation.
I see nobody responded to you. Have you pursued the WebRTC approach and do you have any lessons learned that could be shared with us here regarding
your specific experience regarding the ease in adapting the technology to video chat,
any insights on the basic connection, between two computer instances, that would keep it to a simplest implementation, and
do you have any opinion on whether the technology would be suitable for a person-to-person interaction (text messages containing coordinates of targeted squares) for a simple game such as Battleship?
No. WebRTC in general as a technology base for minimalistic peer-to-peer communications in real-time, regardless of that involving multi-media or just plain text.
I am very much in the early stages of exploring the mechanics for the browser-to-browser communication "layer" for my Battleship game. I like to do "brain-flooding" with relevant material then allow my brain to work things out subconsciously for a while before I try to force my thinking thru the "meat-grinder".
My initial thinking is that it might offer a mechanism to bypass the need for a server as a go-between. Having not yet looked at the implementation examples in detail, I don't yet know if there is a need to use an e-mail message to pass an identifier token, or a uniquely-assigned URL, from the initiator player to the joining player to provide the means for privileged access on the dedicated 2-way channel (or paired channels).
I just don't know yet if it is the optimal, least-overhead, least-complexity approach for implementing the browser-to-browser paired-channel connection ... or not ... for 2-way transmit of intermittent, low-datarate, micro-messaging text-/json-files. I even don't know whether WebRTC is excessive, and whether I could figure out a simpler approach that is WebSockets-based.
... and maybe, WebRTC is that API that simplifies the application of WebSockets for patterns like multi-media or text-exchange (a.k.a. chatting).
Stumbled across this very recent publication about WebRTC: