From: "Enrico Weigelt, metux IT consult" <enrico.weigelt@gr13.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] server push in 9P protocol
Date: Thu, 16 Oct 2014 01:07:55 +0200 [thread overview]
Message-ID: <543EFE4B.80905@gr13.net> (raw)
In-Reply-To: <20141015190323.8864CB82A@mail.bitblocks.com>
Hi folks,
for contigious streaming, we could introduce a new TContRead op,
which tells the server to automatically send new data when available.
Maybe that could also carry some timestamp, so we can synchronize
different streams (eg. audio/video). Of course, this requires some
clear clock reference.
Servers which do not support that, would just reply Rerror, so the
client knows he should try simple TRead loop.
cu
--
Enrico Weigelt,
metux IT consulting
+49-151-27565287
prev parent reply other threads:[~2014-10-15 23:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-15 15:56 smiley
2014-10-15 16:53 ` andrey mirtchovski
2014-10-15 16:55 ` Skip Tavakkolian
2014-10-15 17:14 ` Fran. j. Ballesteros
2014-10-15 17:18 ` David du Colombier
2014-10-15 18:27 ` erik quanstrom
2014-10-15 17:01 ` Bakul Shah
2014-10-15 18:29 ` erik quanstrom
2014-10-15 19:03 ` Bakul Shah
2014-10-15 23:07 ` Enrico Weigelt, metux IT consult [this message]
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=543EFE4B.80905@gr13.net \
--to=enrico.weigelt@gr13.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).