Received: from ATHENA-AS-WELL.MIT.EDU by po7.MIT.EDU (5.61/4.7) id AA21082; Thu, 21 Jan 93 15:27:37 EST
Received: from NOBUNAGA.MIT.EDU by Athena.MIT.EDU with SMTP
	id AA27845; Thu, 21 Jan 93 15:27:28 EST
Message-Id: <9301212027.AA27845@Athena.MIT.EDU>
Received: by ceci.mit.edu id AA00836g; Thu, 21 Jan 93 15:27:25 EST
Date: Thu, 21 Jan 93 15:27:25 EST
From: Tomi Tominaga <htomi@ceci.mit.edu>
To: aybee@Athena.MIT.EDU
Cc: jud@Athena.MIT.EDU, htomi@ceci.mit.edu
In-Reply-To: aybee@Athena.MIT.EDU's message of Thu, 21 Jan 93 13:56:41 EST <9301211856.AA21789@ceci005.MIT.EDU>
Subject: Networking Chapter 


I add in response to your comments ...

1)"object location service"
  I devised this word in the specification to resolve addresses of objects 
  in the same address space.   I thought this module is necessary when an 
  object in a process is addressed from an object in another address space. 
  But there might be a better name for it.  

  And I doubt that I really grasp the meaning of object management.
  I have to study.

2)"SAP"
  To avoid an implementation specific term such as a port in Unix or 
  Macintosh, I quoted this word from OSI reference model. A SAP is an access 
  point of a lower layer (eg., IP) from which the upper layer(eg.,TCP) can 
  get serviced. In Unix the SAP in the model corresponds to a port. But in a 
  strict sense, I might be wrong to use this word because the SAP is used to 
  dictinguish between applications in my model.
  I have to create a new word for it.

Thank you.

Tomi.