[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Weird TCP/IP bug?
- To: "J. Scott Penberthy" <JSP@ibm.com>
- Subject: Weird TCP/IP bug?
- From: Christopher Garrigues <7thSon@SPAR.SLB.COM>
- Date: Wed, 20 Jul 88 19:29:00 EDT
- Cc: SLUG@WARBUCKS.AI.SRI.COM, 7thSon@SPAR.SLB.COM
- Character-type-mappings: (1 0 (NIL 0) (NIL :BOLD NIL) "CPTFONTCB") (2 0 (NIL 0) (NIL :ITALIC NIL) "CPTFONTI")
- Fonts: CPTFONT, CPTFONTCB, CPTFONTI
- In-reply-to: <19880720220048.3.JSP@ESCHER>
1define-server0 implements the server end of a protocol while
1define-protocol0 implements the user end of a protocol. a "service" is a
higher level of abstraction which is referred to by the application
usually by using 1invoke-service-on-host0. So, this means that the same
name (2protocol-name0) should be used in both the 1define-server0 and the
1define-protocol 0protocol forms, and a (possibly) different name
(2service-name0) is used in the 1invoke-service-on-host0 form. These names
will appear in your service attribute like this:
Service: 2service-name0 TCP2 protocol-name
0So, your bug was that you were calling the server and user ends of the
protocol by different names.