Newsgroups: comp.unix.programmer
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!snorkelwacker.mit.edu!thunder.mcrcim.mcgill.edu!mouse
From: mouse@thunder.mcrcim.mcgill.edu (der Mouse)
Subject: Re: More questions on sockets
Message-ID: <1991Jun22.161802.576@thunder.mcrcim.mcgill.edu>
Organization: McGill Research Centre for Intelligent Machines
References: <1991Jun14.162215.14657@ncsu.edu> <14446@dog.ee.lbl.gov>
Date: Sat, 22 Jun 91 16:18:02 GMT
Lines: 19

In article <14446@dog.ee.lbl.gov>, torek@elf.ee.lbl.gov (Chris Torek) writes:

> One simple solution is to use a different port each time, along the
> lines of the Sun RPC `port mapper'.  A single meta-server keeps track
> of all active services.  To establish a service, you contact the port
> mapper and say `I want to offer a service'.  It gives you a port
> number.

Uh, Chris, the portmapper I know has the client obtain the port number
(typically by binding to port 0 and then doing getsockname() to find
out what port was actually bound to, but there are exceptions, eg NFS)
and then tell it to the portmapper.  Not the portmapper choosing a port
and telling the client to use it.

					der Mouse

			old: mcgill-vision!mouse
			new: mouse@larry.mcrcim.mcgill.edu