home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: gnu.misc.discuss
- Path: sparky!uunet!europa.asd.contel.com!darwin.sura.net!Sirius.dfn.de!fauern!fauna!immd4.informatik.uni-erlangen.de!ehmeier
- From: ehmeier@immd4.informatik.uni-erlangen.de (Erich Meier)
- Subject: Re: GNU finger
- References: <146dheINNjrl@iraul1.ira.uka.de> <JBRYANS.92Jul20162806@beach.csulb.edu> <BrqB4M.KpH@immd4.informatik.uni-erlangen.de>
- Message-ID: <Brspxt.19o@immd4.informatik.uni-erlangen.de>
- Sender: news@immd4.informatik.uni-erlangen.de (News Administration at faui45)
- Organization: CSD., University of Erlangen
- Date: Wed, 22 Jul 1992 15:05:52 GMT
- Lines: 27
-
- mskuhn@immd4.informatik.uni-erlangen.de (Markus Kuhn) writes:
-
- >jbryans@beach.csulb.edu (Jack Bryans) writes:
-
- >>If your network has mixed endianity, you may not want it. Its protocol
- >>assumes that the hardware representation of numbers is the same on all of
- >>your hosts.
-
- >Then it is definitely NOT a protocol (which by definition is always an
- >exactly specified format and not something like 'send the bytes of this struct
- >on the line'). :-)
-
- No, it's no protocol. GNU finger sends binary structures over the net, which
- MUST fail on different endians on the net.
- Therefore I implemented the cfinger-"protocol" on top of Sun's RPC mechanism.
- That makes finger much more reliable and faster, too.
- I also fixed a few bugs and made extentions to GNU finger.
- For coordinating my changes with the GNU finger developers, I tried to communi-
- cate with the author and failed. So maybe I'll release my own version.
-
- If you're interested in my version, drop me a line.
-
- Greetings,
- Erich
- ---
- Erich Meier e-mail: ehmeier@informatik.uni-erlangen.de
- "Sagt mal, muesst Ihr das am Tag machen?" - unbekannter CIP-Benutzer
-