[ Usenet FAQs | Search | Web FAQs | Documents | RFC Index ]
    Search the FAQ Archives

Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Part8 - Part9 - Single Page

Top Document: INN FAQ Part 6/9: Day-to-day operation and changes to the system
Previous Document: (6.24) Use more than ~100 Feeds on SunOS 4.1 ?
Next Document: (6.26) I don't want all those reject messages from rnews in syslog


(6.25) Speed up NNTP Transfers ("Streaming NNTP")


Normal NNTP uses the following scheme to transfer articles:

Sender                    Receiver
  ---> Ihave <some Message>
   Ok send it to me       <---
  --->  sends the actual message 
   Says 'this was ok'    <---

This procedure uses 2*RTT on the link (rtt = round trip time) plus time
for the actual article transfer. Jerry Aguirre has rewritten NNTP code
so that it now sends a list of message ids to remote which checks it and
returns a value if it is to be sent. With each message sent Streaming NNTP
also sends a new message-id to check so that the flow of news keeps 
streaming.

Advantages of Streaming NNTP are
- Fast even on lines with a high rtt (e.g. satellite links)
- faster than normal nntp
- compatible as innxmit has a autofallback to normal nntp

Disadvantages are
- INN gets more compute intensive
- Streaming NNTP can fill a 64kB line that much that working 
over it via telnet gets a real pain.



Top Document: INN FAQ Part 6/9: Day-to-day operation and changes to the system
Previous Document: (6.24) Use more than ~100 Feeds on SunOS 4.1 ?
Next Document: (6.26) I don't want all those reject messages from rnews in syslog

Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Part8 - Part9 - Single Page


[ Usenet FAQs | Search | Web FAQs | Documents | RFC Index ]

Send corrections/additions to the FAQ Maintainer:
hwr@pilhuhn.de (Heiko W.Rupp)

Last Update December 05 2008 @ 00:13 AM

© 2008 FAQS.ORG. All rights reserved.