1 / 7

Protecting Application Developers: A Client Toolkit for OGSA-DAI

This client toolkit offers a high-level API for simpler interactions with OGSA-DAI services. It aims to shield application developers from complex implementation details and future changes in web and grid standards. By focusing on solid abstractions like Registry and Grid Data Service, this toolkit minimizes specialist knowledge and steps required, ensuring a more stable solution amidst evolving standards. The toolkit's design anticipates the future adoption of Data Resource concept and supports various OGSA-DAI interfaces, providing flexibility and standardized integration across OMII products.

randall-baxter
Télécharger la présentation

Protecting Application Developers: A Client Toolkit for OGSA-DAI

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. Protecting Application Developers – A Client Toolkit for OGSA-DAI Alastair Hume (A.Hume@epcc.ed.ac.uk) Tom Sugden, Mike Jackson, Mario Antonioletti, Neil Chue Hong, Amy Krause and Martin Westhead

  2. OGSA-DAI Client Toolkit • A high-level API for writing client-side interactions with OGSA-DAI services • Aims: • Provide a clear and simple API built around solid abstractions • Minimise specialist knowledge and the number of steps required to achieve results • Protect to the application developer from future changes to the OGSA-DAI interfaces

  3. Solid Abstractions • Registry • Grid Data Service Factory • Grid Data Service • Request • Constructed from Activities • Response • Easily converted to appropriate types, e.g. ResultSet or ResourceSet.

  4. Minimise Specialist Knowledge

  5. Minimise the Number of Steps

  6. Protection From Future Changes • Proposed Web and Grid standards in state of flux • Changes to standards cause changes to the OGSA-DAI interface • Especially OGSI->WS-RF and DAIS • Client toolkit will hide a lot of these changes from the application developer • Client toolkit makes OGSA-DAI a more stable solution in these times of constant change

  7. Future for Client Toolkit • Data Resource concept may replace the GDSF and GDS • Loosens coupling between client toolkit and service architecture • Will work with all future supported OGSA-DAI interfaces – OGSI, WS-RF, WS-I • Automatically switch to the appropriate interface for the service? • Depreciation policy • Standardisation across all OMII products at client toolkit level?

More Related