Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "PDS Client 2.0 Design"

Line 1: Line 1:
 +
The following design is just proposal to replace current Azigo3 architecture and extend [[PDS Client 2.0]]
  
The following design is just proposal to replace current Azigo3 architecture and extend [[PDS Client 2.0]]
+
The PDS Client is packaged as code library and triggered by separate operating system process with permissions of current logged-in user, so each user in the system has his own instance of PDS.
 
+
The PDS Client is packaged as code library and triggered by separate operating system process with permissions of current logged-in user, so each user in the system has his own instance of PDS.
+
  
 
=== Architecture  ===
 
=== Architecture  ===
  
The following three pictures show design of PDS Client 2.0. The given architecture is based on current components of Azigo3 and with potentially new components. Communication with remote servers is the same as shown on [[PDS Client 2.0]] architecture.
+
The following three pictures show design of PDS Client 2.0. The given architecture is based on current components of Azigo3 and with potentially new components. Communication with remote servers is the same as shown on [[PDS Client 2.0]] architecture.
  
 
1) First picture shows components grouped by process on user's machine:
 
1) First picture shows components grouped by process on user's machine:

Revision as of 11:57, 6 April 2010

The following design is just proposal to replace current Azigo3 architecture and extend PDS Client 2.0

The PDS Client is packaged as code library and triggered by separate operating system process with permissions of current logged-in user, so each user in the system has his own instance of PDS.

Architecture

The following three pictures show design of PDS Client 2.0. The given architecture is based on current components of Azigo3 and with potentially new components. Communication with remote servers is the same as shown on PDS Client 2.0 architecture.

1) First picture shows components grouped by process on user's machine:

Pds 2.0 design components.png

2) On the second picture interactions between high-level components is represented:

Pds design 2.0 hi-lvl iterations.png

3) PDS client provides few services

Pds design 2.0 client-server interactions.png

It consists of the following C++ components:

  • Components 2.0#PAUL - Personal Agent Utility Layer (PAUL) - the higher level logic of the PDS Client 2.0
  • Components 2.0#IPC Lib - planned.
  • Components 2.0#Auth Client

Back to the top