Remote Libraries
Another solution to the library issue comes from using completely separate executables (often in some lightweight form) and calling them using a remote procedure call (RPC) over a network to another computer. This approach maximizes operating system re-use: the code needed to support the library is the same code being used to provide application support and security for every other program. Additionally, such systems do not require the library to exist on the same machine, but can forward the requests over the network.
However, such an approach means that every library call requires a considerable amount of overhead. RPC calls are much more expensive than calling a shared library that has already been loaded on the same machine. This approach is commonly used in a distributed architecture that makes heavy use of such remote calls, notably client-server systems and application servers such as Enterprise JavaBeans.
Read more about this topic: Library (computing)
Famous quotes containing the words remote and/or libraries:
“Space isn’t remote at all. It’s only an hour’s drive away if your car could go straight upwards.”
—Fred, Sir Hoyle (b. 1915)
“riding flatcars to Fresno,
Across the whole country
Steep towns, flat towns, even New York,
And oceans and Europe & libraries & galleries
And the factories they make rubbers in”
—Gary Snyder (b. 1930)