Presentation is loading. Please wait.

Presentation is loading. Please wait.

Comparison: “What Was” and “What Might Be”

Similar presentations


Presentation on theme: "Comparison: “What Was” and “What Might Be”"— Presentation transcript:

1 Comparison: “What Was” and “What Might Be”
What’s New in Node 2.0? Comparison: “What Was” and “What Might Be”

2 The First Exchange Network Node

3 Overview of Basic Node Operations
Basic Services NodePing Authenticate NodePing Authenticate Immediate Services Query Query Delayed Services Submit Execute Notify GetStatus Download Submit Process Notify (?) GetStatus Download

4 Explicit response types Authenticate Addition of “domain” element
What’s New in Node 2.0 NodePing Explicit response types “Ready”, “Offline”, and… Authenticate Addition of “domain” element Future support for federated data model Query Parameters are passed as an array of name/value pairs

5 Now includes an “operation” parameter
What’s New in Node 2.0 Submit Now includes an “operation” parameter Status returned with submit response Process Can be used as a synchronous or asynchronous transaction Immediate response: returns a payload Delayed response: returns a Transaction ID Notify Candidate for removal…is it used today?

6 Explicit response types
What’s New in Node 2.0 GetStatus Explicit response types Not embedded in WSDL in 1.1, but valid responses were listed in the Protocol and Spec 1.1 “Approved” status added Download Added “DocumentID” parameter Allows for downloading individual documents

7 Administrative Flow New Data Flow, not part of WSDL Has an FCD and schema like any other flow Used for flow administration Optional to implement Proposed Data Services: GetDocumentMetadata GetErrorReport GetTransactionDetails


Download ppt "Comparison: “What Was” and “What Might Be”"

Similar presentations


Ads by Google