Good Evening Hakkers!
I just wanted to get started with a small (near-)realtime web-rtc data-channel based pet project. Since I still yet had no time to really get in touch with akka-streams, I wanted to take the akka approch. Imagine: If you could bidirectional connect your javascript application with your akka host with (unreliable) udp latency or multiple multiplexed "reliable" channels with guaranteed delivery order each. How AWESOME would be that (just put aside the whole audio/video crap for a moment)!
The problem is, that there seem to be no real WebRTC Peer (not mediator) JVM based implementation yet - there is only a very googlish java layer above some (wild guess) classical blocking io native code.
So it could not be so hard to implement this protocol on top of akka-streams (the akka-http-core looks pretty straight forward)! Well thats what I thought until I discovered the skyscraper protocol stack that is definde in
http://tools.ietf.org/id/draft-ietf-rtcweb-data-channel-11.txt and its companions wich includes WebRTC using ICE to negotiate a port-knocked SCTP over DTLS over UDP "channel" to a peer. So before I start to dive into such a pet project to make another pet project possible in the first place (which somehow happens far too often :)), I just want to double check if somone else has this on his wish-, todo-, thought-through-it/bad-idea- list.
Kind regards
Daniel