Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!zaphod.mps.ohio-state.edu!brutus.cs.uiuc.edu!psuvax1!psuvm!YKTVMX!RUBIN From: RUBIN@YKTVMX.BITNET (Bill Rubin) Newsgroups: bit.listserv.policy-l Subject: Re: A new LISTSERV Message-ID: Date: 12 Feb 90 15:06:06 GMT Sender: Discussion about BITNET policies Reply-To: Discussion about BITNET policies Lines: 16 Approved: NETNEWS@PSUVM Gateway If enough people were running RSCS V2.2+ or 2.3, you could use the built in list processor feature. Then, all LISTSERV-like software would have to do is send out a single copy of the file with a distribution list, and RSCS, the guy who already KNOWS the topology of the network, would send the minimum number of files. Voila, no more duplication of topology information. This is how things work in VNET, and we do quite a bit of mailing list traffic here, too. Does JNET support this feature? All you really need is the ability to handle multiple dataset headers, which is how MVS manages to be compatible, even though it cannot process the initial distribution list. Note also, that the initial list processor doesn't even have to be on the same machine as the mailing list generator, it can send it to a different node for list processing. Bill Rubin IBM TJ Watson Research