Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!jarthur!nntp-server.caltech.edu!ptimtc!rdmei!icspub!astemgw!wnoc-tyo-news!cs.titech!titccy.cc.titech!necom830!mohta
From: mohta@necom830.cc.titech.ac.jp (Masataka Ohta)
Newsgroups: comp.unix.internals
Subject: Re: Shared libraries
Message-ID: <161@titccy.cc.titech.ac.jp>
Date: 7 May 91 09:58:03 GMT
References: <19239@rpp386.cactus.org> <1991Apr29.031351.3912@decuac.dec.com> <kre.673335935@mundamutti.cs.mu.OZ.AU> <1991May4.132632.13885@mp.cs.niu.edu>
Sender: news@titccy.cc.titech.ac.jp
Organization: Tokyo Institute of Technology
Lines: 19

In article <1991May4.132632.13885@mp.cs.niu.edu>
	rickert@mp.cs.niu.edu (Neil Rickert) writes:

>>and even more importantly, the ability to make changes to library
>>routines that affect all processes to use the library after the change,
>>without recompilation or re linking (other than normal shared library
>>runtime linking).

> On the other hand, I understand your point.  It allows you to take old code
>using the hosts tables, and have it suddenly use the nameserver, for example.

The reality is a bit different. With DNS, it is common that a signle hostname
have multiple IP addresses. Programs were modified so that they try all
possible addresses, because it was common that some of IP addresses are
often unreachable because of a routing problem.

Not so many specification change can be handled simply by replacing libraries.

							Masataka Ohta