home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.protocols.tcp-ip.ibmpc:7378 comp.sys.novell:11371
- Newsgroups: comp.protocols.tcp-ip.ibmpc,comp.sys.novell
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!howland.reston.ans.net!spool.mu.edu!agate!dog.ee.lbl.gov!hellgate.utah.edu!fcom.cc.utah.edu!gateway.univel.com!ns.novell.com!ithaca.Eng.Sandy.Novell.COM!dmurphy
- From: David_Murphy@Novell.COM (David Murphy)
- Subject: Re: ODI information requested.
- Message-ID: <C0qzJs.MpM@Novell.COM>
- Sender: usenet@Novell.COM (Usenet News)
- Nntp-Posting-Host: ithaca.eng.sandy.novell.com
- Organization: Novell, Inc.
- References: <1iskr9INNqfs@usenet.INS.CWRU.Edu> <1993Jan11.155845.62631@cc.usu.edu> <1993Jan12.122554.16503@infodev.cam.ac.uk>
- Date: Tue, 12 Jan 1993 15:40:39 GMT
- Lines: 13
-
- ODI is protocol indepent hence adding code to own Port Number in TCP/IP, etc.
- would break the idea of Protocol indepence in ODI.
-
- Adding a shim which could grab the data from the LSL before it gets to the
- revelent Protocol Stack and distributing to the different IP Stacks is possible
- to do, just envolved and would require some care in implementation.
-
- AS the saying go's, given enough time everything is possible in Software.
-
- David_Murphy@novell.com All opinions are my own, not the employer's
- And I am not a support person either, so
- support questions should go to support people.
-
-