The Opera widget runtime for Desktop implements security features which are in place for mobile devices, but are needed for desktop as well: http://dev.opera.com/articles/view/the-opera-widgets-runtime-for-desktop/ http://www.opera.com/docs/specs/presto24/widgets/#sec
You probably don't want a widget to send files from your file system to remote servers, or to modify files on your filesystem without permissions. That means, there is a security sandbox integrated into the runtime. Opera supports the default Widgets security model. The following points are > a summary of the Opera default security model for Widgets. 1. Opera silently denies direct access to resources residing on a user's > file system. 2. Opera allows a Widget to access content over the Widget protocol. 3. Opera denies access to the end-user's file system over the file: URI > scheme. 4. In the presence of a protocol element, Opera grants a Widget access to > protocols that it supports through the appropriate URI scheme (e.g., ftp, > etc.). In the absence of protocol elements, Opera allows a Widget to access > content over the http and https protocols. 5. Opera allows communication over default ports, or only to the ports the > author has pre-declared as ports using the port element. Opera, > however, denies Widgets from using ports equal to or below 1023 that are not > default ports, even if access is requested by the author via the port > element. - Raju On Fri, Dec 17, 2010 at 7:59 PM, Founder <[email protected]> wrote: > THX 4 your help! I will look at the links later. > > Best, > Duke2010 > > PS: when I want to deploy dthml as a Desktop widget I see no link to mobile > devices ;) > > > -- > Sent from Ubuntu > > > > Raju Bitter wrote: > > Check the list of standards and other links on this page. > http://wiki.kamijs.com/mobile_and_w3c_widgets > > > > Allowing access to the internet depends on the widget standard you > choose. Check the W3C standard proposal as an example: > > http://www.w3.org/TR/2009/WD-widgets-access-20091208/ > > > > Or the Opera standard (although Opera widgets will be discontinued): > http://dev.opera.com/articles/view/opera-widgets-specification-fourth-ed/#xml_security_access > > > > Again, this is something which should be discussed on the mobile > OpenLaszlo mailing list: http://www.openlaszlo.org/mailman/listinfo/mobile > > > > - Raju > > > > On Fri, Dec 17, 2010 at 9:03 AM, Founder <[email protected]> wrote: > > Hi, > > I have an dhtml app running fine on the web as SOLO in any browser, Now for > ubuntu I want to deploy it as a widget: > > Opera or W3W? What is the difference? > > The main issue is, that my app reads xml from the server. The widget is set > to read from the internet, if you will. > Issue now is after installing the app as widget, that it does not get its > data from the internet as when it runs in > the browser. > > So, flash and dhtml have the rule set that all stuff must be in the same > folder. How do you interpret this for an > widget on your desktop.. Must lazlo tomcat run in the background or what? > How do I make the app as widget > obtain its data via TCP?! > > Best, > Duke2010 > > PS: OL is cool, but "tricky.." > > > -- > Sent from Ubuntu > > > > > >
