home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.next.programmer
- Path: sparky!uunet!paladin.american.edu!howland.reston.ans.net!usc!cs.utexas.edu!asuvax!ncar!mimbres.cs.unm.edu!droid!bbum
- From: bbum@stone.com
- Subject: Re: Passing Stream Data between Client and Server?
- Message-ID: <1993Jan22.185942.412@stone.com>
- Sender: bbum@stone.com
- Reply-To: bbum@stone.com
- Organization: Stone Design Corp
- References: <1993Jan22.111601.15395@informatik.uni-hamburg.de>
- Date: Fri, 22 Jan 1993 18:59:42 GMT
- Lines: 27
-
- In article <1993Jan22.111601.15395@informatik.uni-hamburg.de>
- becker@informatik.uni-hamburg.de (Ulrich Becker) writes:
- > In article <1993Jan18.203809.6077@ornl.gov> woo@ornl.gov (John W. Wooten)
- writes:
- > > [Problem description]
- > >
- > > The problem is that NXStreams can't be used between proxy objects since
- > > the size of the NXStream can't be determined. The information can't be
- > > passed as char * since there are imbedded nulls.
- > >
- >
- > Why not use bit/byte stuffing?
-
- If one responds to the NXEncoding/NXDecdoing protocol, then you could create
- a wire compatible object that either uses encode/decodeBytes:count: or pass
- an NXData object between the two hosts....
-
- > > [John W. Wooten]
- >
- > Ulrich Becker
- >
- > Becker@informatik.uni-hamburg.de
-
- b.bum
- --
- <bbum@stone.com> | "I ride tandem with the random...
- Stone Design Corp | ...things don't run the way I planned them." p.gabriel
-