HOW does RSS work?

Don't you get pissed-of when these on-line explanations
just talk about "It's a better EXPERIENCE and 'life is better
with coke'..".

I want to speak with the injun-year not the sales-clerk!!

The folowing level of detailed explanation for USEnet is what I need,
to evaluate RSS:
* the messages are regularly distributed to the servers, which
have a mechanism to update only messages which are new:
each message has an 'IDnumber'.
* the clients post their messages, specifying the Group/s and
Subject.
* the clients can d/l N of the newest message-headers from groups
which are subscribed to.
* after the client-user has read and selected any header-bodies,
which seem potentially interesting, these selected messages
[total of head and body] can be d/l-ed; possibly at a later
on-line session.
* since each message has an IDnumber and the IDnumber of the
message that it is replying to, if it IS a reply, the messages of
the original 'Subject' can form a tree; since multiple replies
to a single message, correspond to the branching of the node
into descendants.

In contrast, blogs offer NO indexing or selection within a
single thread: the whole, perhaps 200 messages must be
d/l-ed TWICE if you want to ask a question and check for a
reply. OTOH USEnet requires only:
d/l-ing the header tree and identifying messages that are
answers to YOUR query, within the message tree.

The result is that blog-commenters of popular blogs,
post their comments 'early' without having time to
sleep over ideas, and consequently give only superficial
input. I.e. the early commenters pay' for small traffic-loads,
and the last commenter has to pay 'the biggest d/l.

So what are the corresponding mechanisms of RSS?

==TIA.

["Followup-To:" header set to comp.os.linux.networking.]
On 2011-05-08, (E-Mail Removed) <(E-Mail Removed)> wrote:
> [snip]
> So what are the corresponding mechanisms of RSS?
>==TIA.
>
You can find the complete RSS specification here:
http://www.rssboard.org/rss-specification