Graphical design component

r3 - 09 Jan 2007 - 00:00:00 - MoinMoin?You are here: TWiki >  TAPIR Web > FifthProposalProviderServiceProposal

5th Provider Service Proposal

General strategy

Treat a provider service as a local MessageBrokerService.

Files

Details

  • optionally listing addressed datasources in the header. If none is mentioned the request should by default be passed on to all available local datasources.
  • All requests are passed on to the requested datasources. EXCEPT:
  • A PingRequest is never relayed to other services and will always be answered directly by the ProviderService.
  • A ProviderService should have its own metadata added to the individual metadata responses of a DatasourceService
  • A ProviderService does not have any additional capabilities (just pooling datasource capabilities responses).
  • Use the same way to call providers:
  • Using a single POST or GET parameter called "request" which contains either the XML message or an URL pointing to the XML message.
  • Use the same error handling strategy:
  • use common Error Codes and prefixes for classification of codes.
Edit | Attach | Printable | Backlinks: Web, All Webs | History: r3 < r2 < r1 | More topic actions
 
Back to TDWG Homepage TDWG Wiki > TAPIR
This site is powered by the TWiki collaboration platform

Valid XHTML 1.0 Transitional
Copyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback