Skip to main content

Cooperating with other APIs

  • Chapter
Practical API Design
  • 1306 Accesses

Abstract

APIs are unlikely to live alone. They don’t do anything interesting on their own; they need to be called. That means the primary concern for an API is to be designed in a way that allows smooth incorporation into a bigger application and easy coexistence with other APIs.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 44.99
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 59.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info
Hardcover Book
USD 79.99
Price excludes VAT (USA)
  • Durable hardcover edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

Bibliography

  1. Joshua Bloch, Effective Java (Upper Saddle River, NJ: Prentice Hall, 2001).

    Google Scholar 

Download references

Rights and permissions

Reprints and permissions

Copyright information

© 2008 Jaroslav Tulach

About this chapter

Cite this chapter

(2008). Cooperating with other APIs. In: Practical API Design. Apress. https://doi.org/10.1007/978-1-4302-0974-4_10

Download citation

Publish with us

Policies and ethics