If this Brick is connected via USB to a computer, a program called Brick Daemon has to be installed. It acts as a translator between TCP/IP and USB. Some Master Extensions can be used to create a direct TCP/IP connection without the need of another computer in between. One example for it is the WIFI Extension.
After receiving a package, the Brick performs the task specified in the delivered
data. For example in case of a
getTemperature() call the Brick will read the
temperature and send it back. The initial function call blocks until the
data package is received and returns the temperature.
In case of calling a Bricklet function, data is send to the Brick where the Bricklet is attached. The Brick calls the corresponding function.
The Bricklet function called, is initially stored together with other data e.g. UID (together called plugin), in the EEPROM on the Bricklet. At start up, this function (with other Bricklet functions if any) is loaded (as position independent code) into the connected Brick Flash. When the Brick calls the corresponding Bricklet function, this function is already loaded inside the Bricks Flash. This generic approach makes it possible to have compatibility between all Bricks and Bricklets, including future ones.
The Programming Interface is available for Windows, Linux and macOS as well as mobile operating systems, such as Android, iOS and Windows Phone.
See this tutorial for more information on how to use it and an idea of the Brick and Bricklet concept.