From: beto@ncube.com beto@ncube.com
Subject: [9fans] IL question?
Date: Fri, 17 Oct 1997 09:50:34 -0700 [thread overview]
Message-ID: <19971017165034.hRlRbaYW8hBHDGcUnW3CyT8kyF59wFGbvHG0_Hveqc8@z> (raw)
In <199710170433.AAA03255@sulphur.osf.org>
Rich Salz <rsalz@opengroup.org> wrote:
> >I don't think it's good idea to add very complex flow control
> >scheme to avoid this problem.
>
> Can't you run over TCP in cases where the lightweight solution isn't
> good enough?
>
I think the fact that IL does not have flow control is not a real
problem because it's use for RPC. However, we are trying to make
the system a little more robust, so I'd like to protect IL for a
miss behaving process which writes a lot of data to the stream.
One of our QA guys decided to test IL and complained about this
problem :-(.
next reply other threads:[~1997-10-17 16:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-10-17 16:50 beto [this message]
-- strict thread matches above, loose matches on Subject: below --
1997-10-17 17:46 presotto
1997-10-17 17:36 beto
1997-10-17 17:09 presotto
1997-10-17 4:33 Rich
1997-10-16 23:40 beto
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=19971017165034.hRlRbaYW8hBHDGcUnW3CyT8kyF59wFGbvHG0_Hveqc8@z \
--to=beto@ncube.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).