Results 1 to 9 of 9

Thread: Firefox 22 Beta Enables WebRTC Support

  1. #1
    Join Date
    Jan 2007
    Posts
    14,604

    Default Firefox 22 Beta Enables WebRTC Support

    Phoronix: Firefox 22 Beta Enables WebRTC Support

    Just days after the Mozilla Firefox 21 release, the first beta of the next Firefox 22 release is now available...

    http://www.phoronix.com/vr.php?view=MTM3NDM

  2. #2

    Default

    Finally. If Firefox starts to support it in the stable version soon, there will be much faster adoption for WebRTC.

    I for one can't wait until they adopt the VP9 codec in WebRTC (and replace VP8), which hopefully will happen this year with some 1.1 update or something.

  3. #3
    Join Date
    Jan 2009
    Posts
    1,646

    Default

    Out of curiosity how is this supposed to work. I mean for emails you have a specific email address for IM a whatever you use address (ie jabber) for phones you have numbers and so on.

  4. #4
    Join Date
    Dec 2011
    Posts
    2,023

    Default Gtk 3

    I want to see Gtk 3 support, Wayland support, and support for <details> and <summary>.

    Also better support for new HTML5 form validation input type=[date|time|number|color].

    Also better support for <menu> and CSS filters such as blur/monochrome/sepia/hue-rotate, etc.

  5. #5
    Join Date
    Jan 2013
    Location
    Sweden
    Posts
    45

    Default

    Quote Originally Posted by 89c51 View Post
    Out of curiosity how is this supposed to work. I mean for emails you have a specific email address for IM a whatever you use address (ie jabber) for phones you have numbers and so on.
    For WebRTC you have URLs. That simple really . Take a look at this: https://apprtc.appspot.com OR this! https://webrtc-experiment.appspot.co...creen-Sharing/
    The 2nd one is my fav! Full screen sharing dammit, just like Skype. I tried it in Chrome Canary!(like Firefox nightly).
    1st example asks you if you allow the webpage to have camera as input and microphone as input. 2nd example you type a room name(doesn't work for Firefox. I've only tested in Chrome Canary, so better wait for Chrome/Chromium stable)

  6. #6
    Join Date
    Jan 2009
    Posts
    1,646

    Default

    Quote Originally Posted by powdigsig View Post
    For WebRTC you have URLs. That simple really . Take a look at this: https://apprtc.appspot.com OR this! https://webrtc-experiment.appspot.co...creen-Sharing/
    The 2nd one is my fav! Full screen sharing dammit, just like Skype. I tried it in Chrome Canary!(like Firefox nightly).
    1st example asks you if you allow the webpage to have camera as input and microphone as input. 2nd example you type a room name(doesn't work for Firefox. I've only tested in Chrome Canary, so better wait for Chrome/Chromium stable)
    Yes but does this mean that everyone will get his own specific url? Like an email address.

  7. #7
    Join Date
    Jan 2013
    Location
    Sweden
    Posts
    45

    Default

    Quote Originally Posted by 89c51 View Post
    Yes but does this mean that everyone will get his own specific url? Like an email address.
    I don't know but I don't think so. The url you connect to is like this https://apprtc.appspot.com/ but when you connect you are assigned a number so it becomes like ie. https://apprtc.appspot.com/?r=70671769
    So the domain appspot.com is the service provider just like Skype.com is a Skype call provider(though no other competing providers are possible in Skype afaik) and ekiga.net is a VoIP provider.
    In VoIP there are addresses like emails foobar@ekiga.net. In webRTC I don't think so. Though you could visit a page called ekiga.net/users/foobar possibly if you want to call foobar. Wouldn't that be awesome?

  8. #8

    Default

    Quote Originally Posted by 89c51 View Post
    Yes but does this mean that everyone will get his own specific url? Like an email address.
    WebRTC specifies the codecs and the protocol but there are different methods possible and its upto the implementation to decide how to do that. This is a very rapidly evolving standard. One possibility is

    http://blog.printf.net/articles/2013...naling-server/

  9. #9
    Join Date
    Jan 2009
    Posts
    1,646

    Default

    Quote Originally Posted by RahulSundaram View Post
    WebRTC specifies the codecs and the protocol but there are different methods possible and its upto the implementation to decide how to do that. This is a very rapidly evolving standard. One possibility is

    http://blog.printf.net/articles/2013...naling-server/
    Thanks.

    Hopefully someone will implement it on top of current IM/email so you can have it working with your own address. Its getting stupid with all those different services.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •