Return to BSD News archive
Path: sserve!manuel!munnari.oz.au!sgiblab!zaphod.mps.ohio-state.edu!sdd.hp.com!uakari.primate.wisc.edu!ames!agate!soda.berkeley.edu!wjolitz From: wjolitz@soda.berkeley.edu (William F. Jolitz) Newsgroups: comp.unix.bsd Subject: Re: STREAMS FOR 386BSD Message-ID: <15cj4fINNs49@agate.berkeley.edu> Date: 31 Jul 92 23:42:07 GMT References: <1992Jul30.210037.9265@ninja.zso.dec.com> <1992Jul31.002259.29940@gateway.novell.com> <1992Jul31.213144.27879@gateway.novell.com> Organization: U.C. Berkeley, CS Undergraduate Association Lines: 18 NNTP-Posting-Host: soda.berkeley.edu There is work underway on a streams-like mechanism for 386BSD called CURRENTS. Among other things, CURRENTS manages to allow for both sockets and TLI or mixtures of both. It is heavily object-oriented, and manages to allow for very small new streams protocol modules to be written and added. It manages to do most of it's processing in the put routines, implements flow control in a novel fashion, and avoids unecessary context switching. CURRENTS must almost certainly be incompatible with USL's streams within the kernel, and obviously won't implement the existing streams drivers. However, it won't suffer from the drawbacks of STREAMS/TLI either. We are walking on brand new ground with this, and if you are extrodinarily experienced in this area, and have the time, dedication, and guts for this, please get in touch with us. Bill.