1 / 5

Most Procedure Calls provide Application Specific access to data.. e.g:

It appears that RPC over http has gained adoption largely because it can be deployed easily over existing infrastructure and configurations (you don’t need IT to be opening ports in corporate firewalls like you do with CORBA).

boaz
Download Presentation

Most Procedure Calls provide Application Specific access to data.. e.g:

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. It appears that RPC over http has gained adoption largely because it can be deployed easily over existing infrastructure and configurations (you don’t need IT to be opening ports in corporate firewalls like you do with CORBA) Local APIs don’t have to worry about finding and binding to available interfaces across system boundaries. Most Procedure Calls provide Application Specific access to data.. e.g: getCalendarEntry(Date, Time) Database engines provide controlled access to data schema and elements in a totally application agnostic way… enabling you to build ANY application (supported by the data) or mine the data for new value XDI can provide the advantages of http based (SOAP based can even leverage existing XML routing hardware) transfer protocols while enabling Application Agnostic, Controlled, data access to remote distributed data sources. While these protocols can be used across system boundaries (very common in J2EE to use JDBC from an app server to a DB server) it generally only works in very tightly controlled environments and configurations for it not to become a security nightmare. None of these protocols natively deal with distributed data. Author: Andy Dale, XDI.ORG

  2. XDI graph elements Nodes Physical Resource Link Logical Data Arcs Type XRI only Ref Instance Backref Version Data orXMLResource

  3. Authority delegation Delegation between Physical Authorities Nodes Physical Resource Link Logical Data Delegation between Logical Authorities Type Arcs XRI only Instance Ref Backref Version Data orXMLResource

  4. Graphing a link contract !!1000 !!1001 Physical /(=A) /(=A*(=B)) /(=B) /(=A) /(=A*(=B)) Logical *(=B) *(=B) /(+email) /($contract) /(+email) /($contract) Type /personal /personal /personal /personal Instance /($v/3) /($v/1) /($v/3) /($v/1) Version *(=A/(+email)/personal/($v/3)) *(=A/(+email)/personal/($v/3)) Data orXMLResource

  5. Author’s Path vs. Rights Path “Author’s Path” “Rights Path” !!1000 !!1001 Physical /(=A) /(=A*(=B)) /(=B) /(=A) /(=A*(=B)) Logical *(=B) *(=B) /(+email) /($contract) /(+email) /($contract) Type /personal /personal /personal /personal Instance /($v/3) /($v/1) /($v/3) /($v/1) Version *(=A/(+email)/personal/($v/3)) *(=A/(+email)/personal/($v/3)) Data orXMLResource

More Related