home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!uwm.edu!psuvax1!psuvm!cjs
- Organization: Penn State University
- Date: Tue, 15 Dec 1992 11:03:48 EST
- From: Christopher Sacksteder <CJS@psuvm.psu.edu>
- Message-ID: <92350.110348CJS@psuvm.psu.edu>
- Newsgroups: bit.listserv.netnws-l
- Subject: Re: VLIB's getting corrupted...
- References: <NETNWS-L%92121508262469@VM1.NODAK.EDU>
- Lines: 14
-
- I don't have a solution for the Netnews problem, but I've been neglectful
- about long member names in VLIB. We never anticipated use of very long
- member names, so we didn't bother to figure out various limitations.
-
- I am changing VLIB EXEC to fail on an ADD request when the member name is
- longer than 222. By experimentation, this seems to be where VLIBCOMP
- fails in parsing a member header (not sure why). A limit that is easier
- to identify is 256, which is the maximum sort field length for RXQSORT
- (called whenever a member is added).
-
- Since NETNEWS should be able to handle messages ids longer than 256, I
- wonder if it couldn't use the article number (unique within groups) for
- the member name (which I believe was my suggestion In The Beginning).
- There would be a minor performance advantage for VLIB ADD.
-