Path: utzoo!attcan!uunet!husc6!bloom-beacon!EXPO.LCS.MIT.EDU!rws
From: rws@EXPO.LCS.MIT.EDU (Bob Scheifler)
Newsgroups: comp.windows.x
Subject: Re: A Simple Question
Message-ID: <8811172224.AA00088@EXPO.LCS.MIT.EDU>
Date: 17 Nov 88 22:24:53 GMT
References: <8811171957.AA07919@savax.Sanders.COM>
Sender: daemon@bloom-beacon.MIT.EDU
Organization: The Internet
Lines: 19


    By reading the protocol spec and using 
    some common sense one should be able to determine what the
    correct behavior is, right?

Right.  The R3 protocol document is (hopefully) clear on Alloc errors:

The server failed to allocate the requested resource.
Note that the explicit listing of
.PN Alloc
errors in request only covers allocation errors at a very coarse level
and is not intended to cover all cases
of a server running out of allocation space in the middle of service.
The semantics when a server runs out of allocation space are left unspecified,
but a server may generate an
.PN Alloc
error on any request for this reason,
and clients should be prepared to receive such errors and handle
or discard them.