Isn’t this a little simplistic ? API’s represent elements of programming libraries available to programmers to customise functionality of an application or language. The concept of of an API is not machine, operating system, network or internet specific. An API is like a screwdriver set, it is a suite of tools for specific tasks.

Java for instance has very many API’s and the great thing about this is that you really only have to learn the API relevant to what it is you actually want to do with a language.

So, your interests are in programming live web applications for editing sound - so then you learn all of the interfaces, methods and libraries of the Java sound API, the GUI part of the API and any relevant web-related API information. You don’t need to pick up the database or 3D API’s as they are peripheral to your programming needs.

The API encapsulates specific functionality and allows a programmer access to the methods and functions of an existing application (i.e. program) or language and allows them to develop their own novel uses or even to extend the API for previously unthought of uses.

You have to understand that my audience would be full of people who have zero understanding of programming concepts.

Many would be struggling with even the concept of Web 2.0, forget getting into the ins and outs of the Java api. At best, they’d merely want to know how to create a small widget using AJAX or PHP. More likely, they would be wondering what the heck it is that their tech-savy subordinate is going on about regarding APIs.

yeah mate.. I was just painting in a few empty spots in the corners but I do understand... explaining technical issues to the layperson can be hell... ever tried to explain General Relativity to someone who has no idea ? That can be great fun...

I was blethering on a wee bit... forgive me.

cheers
:)