874
edits
Labs/Ubiquity/0.2 Design: UI and Security Extensibility: Difference between revisions
Labs/Ubiquity/0.2 Design: UI and Security Extensibility (view source)
Revision as of 20:12, 16 December 2008
, 16 December 2008→Security Extensibility: moved some text around
(Added links to pictures) |
(→Security Extensibility: moved some text around) |
||
| Line 40: | Line 40: | ||
== Security Extensibility == | == Security Extensibility == | ||
The main idea here is to decouple Ubiquity's user interface from its implementation so that it's easier to experiment with more secure implementations | The main idea here is to decouple Ubiquity's user interface from its implementation so that it's easier to experiment with more secure implementations. | ||
In Ubiquity 0.1, command authors create a command feed by inserting an tag of the following form in the <tt><nowiki><HEAD></nowiki></tt> element of an HTML document: | In Ubiquity 0.1, command authors create a command feed by inserting an tag of the following form in the <tt><nowiki><HEAD></nowiki></tt> element of an HTML document: | ||
| Line 56: | Line 56: | ||
Requirement (1) will provide Feed Plugins with the freedom to implement whatever security model they need, while requirements (2) and (3) will give them the ability to present that model to the end-user in an understandable way. | Requirement (1) will provide Feed Plugins with the freedom to implement whatever security model they need, while requirements (2) and (3) will give them the ability to present that model to the end-user in an understandable way. | ||
It should also be possible for one Feed Plugin to wrap another, creating possibilities for middleware. For instance, a social web-of-trust style model could be layered on top of an object capabilities model, thus providing multiple layers of protection for end-users. | Other possibilities for Feed Plugins include: | ||
* Plugins can be created to unify Ubiquity's UI with other pre-existing forms of web extensibility, like Bookmarklets and Greasemonkey scripts. | |||
* It should also be possible for one Feed Plugin to wrap another, creating possibilities for middleware. For instance, a social web-of-trust style model could be layered on top of an object capabilities model, thus providing multiple layers of protection for end-users. | |||