Geek asks and answers

Socket API: prohibited in packaged applications?

I am trying to use the new Socket API for Chrome extensions, and I am facing a confusing error. The phenomenon for my sample application is as follows:

{
  "name":"Yet Another Socket App",
  "version":"0.0.1",
  "manifest_version":2,
  "permissions":[
    "experimental", "socket"
  ],
  "app":{
    "launch":{
        "local_path":"index.html"
    }
  }
}

The application loads (i.e. no error warnings), but a warning appears under its entry in chrome://extensions:'socket' is not allowed for specified package type (theme, app, etc.).

Notes: index.html Exists and is a simple HTML document (and chrome.socketindeed undefinedinside it). I have included experimental APIs through chrome://flags. I am running the Chrome Dev channel ( v22.0.1229.6 dev) on Ubuntu.

( , Dev), ? , Chrome Stable Dev; , apt-get purge google-chrome-stable rm -rf ~/.config/google-chrome , ?

+5
1

, Google: http://developer.chrome.com/trunk/apps/app_network.html

Chrome

'permissions [1]'

App: https://github.com/GoogleChrome/chrome-app-samples/tree/master/udp

permissions manifest.json

"permissions": [
    "experimental",
    {"socket": [
        "udp-send-to"
    ]},
    "app.window"
]

socket Chrome 23 :

var socket = chrome.socket || chrome.experimental.socket;
+3

More articles:


All Articles