P2P API Appears in About:Flags

Posted on 03. Mar, 2011 by in News

flattr this!

The newest builds of Chromium have a new option that can be enabled through the “about:flags” menu. It’s called P2P API and turns on the P2P Pepper API and the P2P JavaScript API. Yet even in the description, the feature states that it doesn’t even work at this point. So what does it do?

p2papi1
Well, the peer-to-peer connotation here would suggest a connection of sort using both Pepper and JavaScript. Pepper is a plugin that can use Native Client to harness hardware resources. In the notes for the latest Native Client release in February, it is pointed out that peer-to-peer networking is not yet supported, among other APIs such as 3D graphics and file I/O.

So this is being implemented likely to test its compatibility with Native Client. It’s also possible that it’s being used to test Chromoting, another experimental feature in about:flags that doesn’t work unless you are on the dev team for Chromium.

  • services sprite
  • services sprite
  • services sprite
  • services sprite
  • services sprite
  • services sprite
  • services sprite
  • services sprite
  • services sprite

Related posts:

  1. Run PPAPI Flash in the Renderer Process Appears in “About:Flags”
  2. Google Preparing to Fuel Webapp Growth with Native Client for Chrome
  3. Google Changes Flags UI in Chromium

Tags: , , , , , , , , ,

13 Responses to “P2P API Appears in About:Flags”

  1. P2P API Discovered in Latest Builds of Chromium | JetLib News

    11. Mar, 2011

    [...] the open source browser that serves as the basis for Google Chrome. The discovery was made by Daniel Cawrey at thechromesource. The description of the option reads: “Enables P2P Pepper API and P2P JavaScript API. The API [...]

  2. P2P API Discovered in Latest Builds of Chromium Phone Blogging

    11. Mar, 2011

    [...] th&#1077 basis f&#959r Google Chrome. Th&#1077 discovery w&#1072&#1109 m&#1072&#1281&#1077 b&#1091 Daniel Cawrey &#1072t thechromesource. Th&#1077 description &#959f th&#1077 option reads: “Enables P2P Pepper API &#1072n&#1281 P2P [...]

  3. P2P API Discovered in Latest Builds of Chromium | The best Tutorials

    11. Mar, 2011

    [...] the open source browser that serves as the basis for Google Chrome. The discovery was made by Daniel Cawrey at thechromesource. The description of the option reads: “Enables P2P Pepper API and P2P JavaScript API. The API [...]

  4. [...] the open source browser that serves as the basis for Google Chrome. The discovery was made by Daniel Cawrey at thechromesource. The description of the option reads: “Enables P2P Pepper API and P2P JavaScript API. The API [...]

  5. [...] the open source browser that serves as the basis for Google Chrome. The discovery was made by Daniel Cawrey at thechromesource. The description of the option reads: “Enables P2P Pepper API and P2P JavaScript API. The API [...]

  6. P2P API Discovered in Latest Builds of Chromium - Finding Out About

    11. Mar, 2011

    [...] the open source browser that serves as the basis for Google Chrome. The discovery was made by Daniel Cawrey at thechromesource. The description of the option reads: “Enables P2P Pepper API and P2P JavaScript API. The API [...]

  7. [...] the open source browser that serves as the basis for Google Chrome. The discovery was made by Daniel Cawrey at thechromesource. The description of the option reads: “Enables P2P Pepper API and P2P JavaScript API. The API [...]

  8. P2P API Discovered in Latest Builds of Chromium

    11. Mar, 2011

    [...] the open source browser that serves as the basis for Google Chrome. The discovery was made by Daniel Cawrey at thechromesource. The description of the option reads: “Enables P2P Pepper API and P2P JavaScript API. The API [...]

  9. Andrew de Andrade

    11. Mar, 2011

    I hope this is related to an idea I floated about 1.5 years ago on the WHAT-WG working group. Given how mature node.js and evented servers have become this makes even moar sense than it did when I originally tossed the idea about.

    http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2010-January/024772.html

  10. P2P API Discovered in Latest Builds of Chromium | thefinalcastle.com

    12. Mar, 2011

    [...] the open source browser that serves as the basis for Google Chrome. The discovery was made by Daniel Cawrey at thechromesource. The description of the option reads: “Enables P2P Pepper API and P2P JavaScript API. The API [...]

  11. P2P API Discovered in Latest Builds of Chromium | JC

    12. Mar, 2011

    [...] the open source browser that serves as the basis for Google Chrome. The discovery was made by Daniel Cawrey at thechromesource. The description of the option reads: “Enables P2P Pepper API and P2P JavaScript API. The API [...]

  12. [...] the open source browser that serves as the basis for Google Chrome. The discovery was made by Daniel Cawrey at thechromesource. The description of the option reads: “Enables P2P Pepper API and P2P JavaScript API. The API [...]

  13. [...] is different from the old NPAPI version. A while back the Pepper API was added as a feature in Chromium's "about:flags" for JavaScript. Now it's an experiment for Flash-based renderer processes. This new PPAPI will be used for running [...]

Leave a Reply

Name

Email

Website

Comment