Please Whitelist This Site?

I know everyone hates ads. But please understand that I am providing premium content for free that takes hundreds of hours of time to research and write. I don't want to go to a pay-only model like some sites, but when more and more people block ads, I end up working for free. And I have a family to support, just like you. :)

If you like The TCP/IP Guide, please consider the download version. It's priced very economically and you can read all of it in a convenient format without ads.

If you want to use this site for free, I'd be grateful if you could add the site to the whitelist for Adblock. To do so, just open the Adblock menu and select "Disable on tcpipguide.com". Or go to the Tools menu and select "Adblock Plus Preferences...". Then click "Add Filter..." at the bottom, and add this string: "@@||tcpipguide.com^$document". Then just click OK.

Thanks for your understanding!

Sincerely, Charles Kozierok
Author and Publisher, The TCP/IP Guide


NOTE: Using software to mass-download the site degrades the server and is prohibited.
If you want to read The TCP/IP Guide offline, please consider licensing it. Thank you.

The Book is Here... and Now On Sale!

Enjoy The TCP/IP Guide? Get the complete PDF!
The TCP/IP Guide

Custom Search







Table Of Contents  The TCP/IP Guide
 9  TCP/IP Application Layer Protocols, Services and Applications (OSI Layers 5, 6 and 7)
      9  TCP/IP Key Applications and Application Protocols
           9  TCP/IP File and Message Transfer Applications and Protocols (FTP, TFTP, Electronic Mail, USENET, HTTP/WWW, Gopher)
                9  Usenet (Network News) and the TCP/IP Network News Transfer Protocol (NNTP)
                     9  TCP/IP Network News Transfer Protocol (NNTP)

Previous Topic/Section
NNTP Overview and General Operation
Previous Page
Pages in Current Topic/Section
12
3
4
Next Page
NNTP Client-Server Communication Process: News Posting and Access
Next Topic/Section

NNTP Inter-Server Communication Process: News Article Propagation
(Page 3 of 4)

Article Propagation Using the "Push" Model

Here’s how the push model works. When the administrators of an NNTP server establish a service relationship with an upstream Usenet service provider, they furnish the provider with a list of newsgroups that the downstream server wants to carry. Whenever a new article arrives at the upstream server within that list of groups, it is automatically sent to the downstream site. This saves the downstream server from constantly having to ask “has anything arrived?”

In the classical NNTP protocol as defined in RFC 977, the exchange of articles is based on the push model, and performed using the IHAVE command. Suppose three new messages arrive at the largenews server. It would establish an NNTP connection to mediumnews and use IHAVE to provide the message IDs of each of the three new messages, one at a time. The mediumnews server would respond to each one indicating whether it already had that message or not. If not, largenews would send it the message. An example article transaction using the push model of propagation is illustrated in Figure 312.


Figure 312: NNTP Article Propagation Using The “Push” Model

This example shows how Usenet articles are moved between servers using the conventional “push” model of propagation. Here, the device acting as an NNTP client (which recall may in fact be an NNTP server) has two messages available to offer to the server. It sends the IHAVE command specifying the message ID of the first message, but the server already has that message so it sends a 435 “do not send” reply. The client then issues an IHAVE with the second message ID; the server wants this one, so it sends a 335 reply; the client sends the Usenet message, ending with a single period on a line by itself. The server indicates that it received the message and the client, done with its transactions, quits the session.

 


The main advantage of this technique is that it ensures that a server is not sent a duplicate copy of a message that it already has. The problem with it in modern Usenet is that it is slow, because the server must respond to the IHAVE command before the message or the next command can be sent by the client.


Previous Topic/Section
NNTP Overview and General Operation
Previous Page
Pages in Current Topic/Section
12
3
4
Next Page
NNTP Client-Server Communication Process: News Posting and Access
Next Topic/Section

If you find The TCP/IP Guide useful, please consider making a small Paypal donation to help the site, using one of the buttons below. You can also donate a custom amount using the far right button (not less than $1 please, or PayPal gets most/all of your money!) In lieu of a larger donation, you may wish to consider purchasing a download license of The TCP/IP Guide. Thanks for your support!
Donate $2
Donate $5
Donate $10
Donate $20
Donate $30
Donate: $



Home - Table Of Contents - Contact Us

The TCP/IP Guide (http://www.TCPIPGuide.com)
Version 3.0 - Version Date: September 20, 2005

© Copyright 2001-2005 Charles M. Kozierok. All Rights Reserved.
Not responsible for any loss resulting from the use of this site.