Announcement

Collapse
No announcement yet.

Firefox 22 Beta Enables WebRTC Support

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • 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
    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.

    Comment


    • #3
      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.

      Comment


      • #4
        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.

        Comment


        • #5
          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)

          Comment


          • #6
            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.

            Comment


            • #7
              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?

              Comment


              • #8
                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/

                Comment


                • #9
                  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.

                  Comment

                  Working...
                  X