Home - api. Home - api. IssueMap : Home.
Ping.fm. Meaningtool - Create Your Own AI. Klout for Developers. Delicious. Twitter API. Gigya : l'api des apis. SIOC API. Wolfram|Alpha API. Open API technology for content management systems. OAuth API. LinkedIn. Orange API tutoriels - OrangeAPI. Flickr. Ziki. API users & API wrappers. Suppose you have a sparse RAM API, something along the lines of: add_range(base, size)write_ram(base, bytes)read_ram(base, size) People use this API for things like running a simulated CPU: define the accessible memory with add_range()pass the initial state to the simulator with write_ram()run the simulation, get the final state with read_ram() Suppose this API becomes a runaway success, with a whopping 10 programmers using it (very little irony here, >95% of the APIs in this world are used exclusively by their designer).
Then chances are that 9 of the 10 programmers are API users, and 1 of them is an API wrapper. Here's what they do. API users The first thing the first API user does is call you. Add_range(0x100000, 6) # input range add_range(0x200000, 6) # output range write_ram(0x100000, "abcdef") # run a program converting the input to uppercase print read_ram(0x200000, 6) # should print "ABCDEF" It runs. Then some time later you stumble upon the following code: Waitaminnit. API wrappers Why.