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 "I-Card Provider"

(Links)
 
(7 intermediate revisions by one other user not shown)
Line 1: Line 1:
{{#eclipseproject:technology.higgins}}
+
{{#eclipseproject:technology.higgins|eclipse_custom_style.css}}
 
__NOTOC__
 
__NOTOC__
Higgins supports multiple kinds of i-cards with differing characteristics. It does so by using multiple kinds of i-card providers, each of which implements one specific class of i-card. Although all i-cards implement the base "ICard" interface, some may implement one or more of the optional interfaces, and thus provide more or different characteristics. The Higgins project is developing these I-Card Providers:
+
Higgins supports multiple kinds of i-cards with differing characteristics. It does so by using multiple kinds of i-card providers, each of which implements one specific class of i-card. Although all i-cards implement the base "ICard" interface, some may implement one or more of the optional interfaces, and thus provide more or different characteristics.  
# [[CardSpace Managed I-Card Provider]]
+
# [[CardSpace Personal I-Card Provider]]
+
# [[URI Managed I-Card Provider]]
+
# [[URI Personal I-Card Provider]]
+
 
+
==Details==
+
* ''Status:'' since 1.0M7
+
* ''Language:'' Java
+
* ''Packaging:'' OSGI bundle
+
 
+
==Plan==
+
* TODO:link
+
  
 
==Service/API==  
 
==Service/API==  
Line 21: Line 9:
 
* Supporting the [[I-Card Registry]] in importing I-Cards from one of the supported card data formats.  
 
* Supporting the [[I-Card Registry]] in importing I-Cards from one of the supported card data formats.  
 
** [[I-Card Provider]]s implements a ''canImportICard'' method that declares what formats it can support
 
** [[I-Card Provider]]s implements a ''canImportICard'' method that declares what formats it can support
* Supporting the [[I-Card Registry]] in exporting I-Cards to one of the supported card data formats. (Note: this is a change, earlier we had said that export of a single [[I-Card]] is handled by the [[I-Card]] itself)
+
* Supporting the [[I-Card Registry]] in exporting I-Cards to one of the supported card data formats.  
  
[[Category:Components]]
+
[[Category:Higgins Components]]

Latest revision as of 09:37, 15 December 2008

{{#eclipseproject:technology.higgins|eclipse_custom_style.css}}

Higgins supports multiple kinds of i-cards with differing characteristics. It does so by using multiple kinds of i-card providers, each of which implements one specific class of i-card. Although all i-cards implement the base "ICard" interface, some may implement one or more of the optional interfaces, and thus provide more or different characteristics.

Service/API

An I-Card Provider is responsible for:

  • Instantiating I-Cards that implement the I-Card Interfaces
  • Managing the persistence of i-cards (e.g. to/from working storage)
  • Supporting the I-Card Registry in importing I-Cards from one of the supported card data formats.
    • I-Card Providers implements a canImportICard method that declares what formats it can support
  • Supporting the I-Card Registry in exporting I-Cards to one of the supported card data formats.

Back to the top