Talk:WebExtensions/Native Messaging

Host Manifests - location manifest

For Windows manifest file locations, would it also follow similar to chrome in, first the 32-bit registry is queried, then the 64-bit registry? Kattamine (talk) 01:13, 29 April 2016 (PDT)

Good question, I'd like to take this over to bug 1270359 though. aswan (talk) 22:13, 8 May 2016 (PDT)

Host Manifests - version

For a chrome plugin using connectNative, just coming to a situation where we are trying to understand a best way to manage the 2 release cycles of such a plugin and the native component. It seems likely that the native application may be older more often than the plugin especially where they are automatically updated. Mainly an issue when the API is being changed and a consideration for backward compatibility. Would it make sense to add some sort of version to the native manifest, and a version range required in the plugin? Kattamine (talk)

Is there an advantage to handling this within the manifest instead of just creating multiple native manifests (e.g., "myappv1", "myappv2", etc.)? aswan (talk)

Adding version to the <name> might be enough. It would be a 1-1 mapping rather than a range, those that need it have to manage it in the extension by attempting to launch several connections. Kattamine (talk)