[Prev][Next][Index][Thread]

# overflow output buffer

- Date: Sat, 27 Jan 1996 10:41:42 PST
- From:
- cc: phantom@baymoo.sfsu.edu, dave@ipac.caltech.edu, moo-cows.PARC@xerox.com
- Content-Type: text
- In-Reply-to: "<199601271738.MAA14236@vortex.weather.brockport.edu> from \"Chuck Adams\" at Jan 27, 96 10:38:46 am "

    A short while ago, I wrote:

    You need to control the connection by doing 2 things:

            1.  Make sure that you don't overflow the output buffer by using the
                new notify behavior.

    The way to do this is using a construct like

     8:    while (!notify(this, args[1], 1))
     9:      suspend(0);
    10:    endwhile

    which keeps trying until successful to place a line in the output buffer.
    Making the buffer be bigger, by editing options.h (or whatever) will not
    be a robust solution.

    The problem with this code though is that it suspends, thus breaking any
    atomicity you may have been counting on.  If this turns out to be a problem,
    you may want to rethink the design of large atomic tasks.

    - DVB

References:

- Re: Binary IO

- From: cadams@weather.brockport.edu (Chuck Adams)

- Prev: Re: Open_Network_connection
- Next: Re: Panic dump
- Index: MOO-cows
- Thread: MOO-cows

Home | Subject Index | Thread Index