From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Raw Input Driver
Date: Fri, 20 Mar 2009 08:04:06 -0400 [thread overview]
Message-ID: <08eca189ae4603cef81c2f67842af217@quanstro.net> (raw)
In-Reply-To: <6c41ef4c92791aa306e71d4be15901b1@lsub.org>
On Fri Mar 20 07:40:30 EDT 2009, nemo@lsub.org wrote:
> If connection is slow (as the one I'm using now) increasing the
> abstraction level is a good thing to do. Merging low level input
> streams may patch up things for a while, but won't be enough
> if the connection is slower.
i think it does solve the originally stated problem — keeping input
streams in sync, which is a problem for a local viewer if any input-handling
proc does potentially-blocking i/o.
john carmack mentioned this way back when:
http://9fans.net/archive/1995/11/123
i suppose thinking of this as a real-time problem could make sense,
but simply keeping order would seem to me to be a useful subset of the whole
problem.
- erik
next prev parent reply other threads:[~2009-03-20 12:04 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-20 7:00 James Tomaschke
2009-03-20 7:07 ` lucio
2009-03-20 7:57 ` James Tomaschke
2009-03-20 9:12 ` erik quanstrom
2009-03-20 11:05 ` Charles Forsyth
2009-03-20 10:54 ` Francisco J Ballesteros
2009-03-20 11:07 ` cinap_lenrek
2009-03-20 11:28 ` roger peppe
2009-03-20 11:39 ` Fco. J. Ballesteros
2009-03-20 12:04 ` erik quanstrom [this message]
2009-03-20 11:32 ` erik quanstrom
2009-03-20 12:23 ` Charles Forsyth
2009-03-20 12:16 ` erik quanstrom
2009-03-20 13:03 ` roger peppe
2009-03-20 13:37 ` tlaronde
2009-03-20 14:26 ` roger peppe
2009-03-20 15:02 ` tlaronde
2009-03-20 15:14 ` tlaronde
2009-03-20 12:52 ` maht
2009-03-20 22:23 ` James Tomaschke
2009-03-20 9:13 ` lucio
2009-03-20 14:18 Francisco J Ballesteros
2009-03-20 14:29 ` roger peppe
2009-03-20 14:22 Francisco J Ballesteros
2009-03-20 14:32 ` roger peppe
2009-03-20 15:17 ` lucio
2009-03-20 14:35 Francisco J Ballesteros
2009-03-20 14:46 Francisco J Ballesteros
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=08eca189ae4603cef81c2f67842af217@quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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).