From: robin@bateboerop.name (Robin Bate Boerop)
Subject: [9fans] Does 9P provide multicast for files?
Date: Wed, 23 Mar 2011 18:41:10 -0300 [thread overview]
Message-ID: <AANLkTi=ycG5Sa6KDF_hV8QJhh4zTRqNzfmonSyo0Wr_8@mail.gmail.com> (raw)
In-Reply-To: <35e56c75c407ad92ab2d3d9d65ff71ad@brasstown.quanstro.net>
On 23 March 2011 17:55, erik quanstrom <quanstro at quanstro.net> wrote:
> On Wed Mar 23 16:43:55 EDT 2011, paurea at gmail.com wrote:
>> Both readers and writers are clients of a 9p file server. ?It decides
>> who to answer. ?It is not specified by the protocol.
>
> excellent answer.
>
> i'd like to add, though, since tags are chosen by the client,
> the 9p messages can't be multicast at the transport or
> network layer.
>
> so if data becomes available that could unblock both readers
> the file server may pick one, neither, or send the same data
> (with different tags, etc) to both.
Erik and Gorka, thank you for the prompt and clear answers.
prev parent reply other threads:[~2011-03-23 21:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-23 20:23 Robin Bate Boerop
2011-03-23 20:38 ` Gorka Guardiola
2011-03-23 20:55 ` erik quanstrom
2011-03-23 21:41 ` Robin Bate Boerop [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='AANLkTi=ycG5Sa6KDF_hV8QJhh4zTRqNzfmonSyo0Wr_8@mail.gmail.com' \
--to=robin@bateboerop.name \
/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).