Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "PDS Architecture"
(→Data Model) |
(→Front End Components) |
||
Line 15: | Line 15: | ||
[[Image:Higgins-client-2.0.213.png|center]] | [[Image:Higgins-client-2.0.213.png|center]] | ||
− | ===Client=== | + | === Client === |
+ | |||
The client is written in HTML and JavaScript and runs in any desktop browser (e.g. IE, FF, Safari, Chrome). In the future we also plan to make it display well on the limited screen size of smartphone mobile browser (e.g. iPhone, Android, etc.). | The client is written in HTML and JavaScript and runs in any desktop browser (e.g. IE, FF, Safari, Chrome). In the future we also plan to make it display well on the limited screen size of smartphone mobile browser (e.g. iPhone, Android, etc.). | ||
− | ===HBX=== | + | |
− | The Higgins browser extension makes possible functionality that isn't possible in a pure web app architecture. One kind of functionality is browser-side integration with other web APIs and sites. Shown above is a connector that imports the user's advertising preferences from Google's Ad Preference page (http://www.google.com/ads/preferences). | + | === HBX === |
+ | |||
+ | The Higgins browser extension makes possible functionality that isn't possible in a pure web app architecture. One kind of functionality is browser-side integration with other web APIs and sites. Shown above is a connector that imports the user's advertising preferences from Google's Ad Preference page (http://www.google.com/ads/preferences). | ||
+ | |||
+ | *org.eclipse.higgins.js.pds.connector.common | ||
+ | *org.eclipse.higgins.js.pds.connector.gap | ||
== Back End Components == | == Back End Components == |
Revision as of 10:34, 26 August 2011
{{#eclipseproject:technology.higgins|eclipse_custom_style.css}}This document describes the top level Higgins 2.0 PDS components under active development. Here are the bugzilla component names:
- H2-Client
- H2-HBX
- H2-PDS
- H2-PDS Support
- H2-ADS
- H2-Data Model
Contents
Front End Components
There are two front end components: a web client, and a browser extension.
Client
The client is written in HTML and JavaScript and runs in any desktop browser (e.g. IE, FF, Safari, Chrome). In the future we also plan to make it display well on the limited screen size of smartphone mobile browser (e.g. iPhone, Android, etc.).
HBX
The Higgins browser extension makes possible functionality that isn't possible in a pure web app architecture. One kind of functionality is browser-side integration with other web APIs and sites. Shown above is a connector that imports the user's advertising preferences from Google's Ad Preference page (http://www.google.com/ads/preferences).
- org.eclipse.higgins.js.pds.connector.common
- org.eclipse.higgins.js.pds.connector.gap
Back End Components
There are three back end components mostly written in Java and running in the cloud (e.g. Amazon AWS):
- PDS
- PDS Support
- ADS
PDS
PDS Subcomponents:
- .pds.usermanager.ws - simple web service to manage user accounts, change password, etc.
PDS Support
PDS Support Subcomponents:
- .pds.client - wrapper around Open Anzo java client
ADS
ADS Subcomponents:
- PLANNED: .ads.ld - Linked Data endpoint
Data Model
Data attributes whether created by the user or imported from an external service are stored in a common data model. This allows them to be consistently displayed to, and in some cases edited by, the user irrespective of its original source. We call this the Persona Data Model 2.0.