Subject: n lines flushed

From: Kent Pitman <[email-masked]>
Date: Sat, 10 Apr 1993 21:03:51 -0700

In getting caught up on "read new on *soc" (never having read it before)
on lambdamoo, I saw lots of <n lines flushed> and just assumed that it
was lines of long messages that had been judiciously pruned by a wizard
who was trying to compact the database.  The idea that this was network
buffer overflow didn't occur to me until yduJ set me straight just now.
The message should be changed to reflect the real situation so I'd know
to retry my showing of individual messages that got truncated or missing
messages that I didn't end up seeing.  I suggest something like:
 "network buffer overflowed. n lines have been lost"
-kmp (Mickey@LambdaMOO)

---

From: Pavel Curtis <[email-masked]>
Date: Mon, 12 Apr 1993 11:36:05 -0700

> Date:	Sat, 10 Apr 1993 23:55:51 -0700
> From:	[email-masked] (Mike 'What Day is it?' Wilson)
> 
> I think that the 'n lines flushed' line is *not* a product of MOO.

This isn't true; the message *does* come from the MOO server and I have fixed
it along the lines Kent recommended.

The server *must* have such a facility because the underlying network
architecture (TCP) is providing a reliable stream service and therefore must
include some kind of flow control which therefore means that the server may
have to block in sending data to the client.  Thus, the server will sometimes
have to buffer up data for the client and those buffers may at some point
overflow.

	Pavel

---

From: [email-masked] (Mike 'What Day is it?' Wilson)
Date: Mon, 12 Apr 1993 13:03:34 -0700

I guess I jumped the gun on that one.  I haven't looked at either the code
for MOO, not the code for TinyFugue.  Having hence, pondered the idea of
that statement, it makes much more sense for the server to have been doing
it all along.  
Zaphod@VampMOO (Kicking himself for writing a stupid letter after coming
home toasted from a party :))