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.
Difference between revisions of "PDS 2.0"
(→Old Notes) |
|||
| Line 16: | Line 16: | ||
* [[Higgins PDS Access]] - rough notes | * [[Higgins PDS Access]] - rough notes | ||
| − | + | ==Old Notes== | |
*Sending [[XDI]] messages to its endpoint | *Sending [[XDI]] messages to its endpoint | ||
*Using the following low level client libraries: | *Using the following low level client libraries: | ||
Revision as of 11:24, 12 August 2010
{{#eclipseproject:technology.higgins|eclipse_custom_style.css}}
The PDS 2.0 is a work in progress.
This wiki page contains a few pointers, but needs to be rewritten.
Core Service
The PDS is a variant of the IdAS Proxy Service, with the following changes:
- The UDI Resolver is configured to support sync:// UDIs
- The IdAS Registry is configured to include the RDF2 Context Provider.
The IdAS Proxy Service is layered over the Attribute Service 1.1 to provide a bi-directional, synchronizing XDI endpoint over data managed by Context Provider plug-ins to the IdAS package. These context providers area also data adapters to a variety of back end data stores.
Accessing a PDS
Accessing a PDS from an app (aka relying party, service provider) ==
- Higgins PDS Access - rough notes
Old Notes
- Sending XDI messages to its endpoint
- Using the following low level client libraries:
- Org.eclipse.higgins.idas.client (Java IdAS Client)
- Org.eclipse.higgins.idasclient.cpp.core (C++ IdAS Client)
- Using the PDS Client 2.0