Comments on: Apparently GNOME Mobile has a D-Bus/Browser bridge http://www.j5live.com/2008/09/30/apparently-gnome-mobile-has-a-d-busbrowser-bridge/ Where the urethane hits the pavement Mon, 10 Oct 2011 13:34:18 -0400 http://wordpress.org/?v=2.8.4 hourly 1 By: rektide http://www.j5live.com/2008/09/30/apparently-gnome-mobile-has-a-d-busbrowser-bridge/comment-page-1/#comment-19631 rektide Wed, 01 Oct 2008 20:07:38 +0000 http://www.j5live.com/2008/09/30/apparently-gnome-mobile-has-a-d-busbrowser-bridge/#comment-19631 Show me the source. I saw the release via LinuxDevices.com back when Movial made the announcement and have not seen any followup. I've been working on a JSON-RPC exposure for DBus for a while, but it keeps getting put off and heavily restructured, so their code is something I'd love to see. Show me the source. I saw the release via LinuxDevices.com back when Movial made the announcement and have not seen any followup.

I’ve been working on a JSON-RPC exposure for DBus for a while, but it keeps getting put off and heavily restructured, so their code is something I’d love to see.

]]> By: Christopher Blizzard http://www.j5live.com/2008/09/30/apparently-gnome-mobile-has-a-d-busbrowser-bridge/comment-page-1/#comment-19628 Christopher Blizzard Tue, 30 Sep 2008 17:41:30 +0000 http://www.j5live.com/2008/09/30/apparently-gnome-mobile-has-a-d-busbrowser-bridge/#comment-19628 It really depends on what they are doing. If they have XUL components then it makes it possible to connect to D-Bus services via XUL. That's pretty safe since web pages and the surrounding XUL/Chrome are separate. But what I actually suspect they are doing is exposing bus methods through a JS interface that certain web widgets can use via private device APIs. For the most part web widgets look like local apps that are loaded and can load content from the network, but don't always do so. The permissions models for these apps looks a little bit different. It really depends on what they are doing. If they have XUL components then it makes it possible to connect to D-Bus services via XUL. That’s pretty safe since web pages and the surrounding XUL/Chrome are separate.

But what I actually suspect they are doing is exposing bus methods through a JS interface that certain web widgets can use via private device APIs. For the most part web widgets look like local apps that are loaded and can load content from the network, but don’t always do so. The permissions models for these apps looks a little bit different.

]]>