I suggest you take a look instead at the code in media/mtransport. I don't think you would need to change media/webrtc/signaling to do what you want.
-EH On Thu, Jul 11, 2013 at 11:04 AM, peetonn <[email protected]> wrote: > Hi there, > > I'm curious of how does acquiring of video frames and sending them over > the network actually work? > I've looked at media/webrtc/siganling sources as well as read lots of > documents like these (http://tools.ietf.org/html/rfc5245#section-1, > http://datatracker.ietf.org/doc/draft-ietf-rtcweb-jsep/?include_text=1, > http://dev.w3.org/2011/webrtc/editor/webrtc.html#intro and others) but > still can't find a point in a code where frames are acquired and sent to > the udp socket. There are MediaStream, MediaConduit, MediaPipeline, > CC_SIPCCCall, CC_SIPCCDevice... and all of this is highly interconnected. > > What I'm trying to do in the end - is to substitute default UDP-transport > with another one (specifically this one http://www.named-data.net/). So I > need to understand in which way it is possible to do. > Will appreciate any help and ideas where to look at... > _______________________________________________ > dev-media mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-media > _______________________________________________ dev-media mailing list [email protected] https://lists.mozilla.org/listinfo/dev-media
