From: "Francisco J Ballesteros" <nemo@lsub.org>
To: weigelt@metux.de,
"Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] 9P vs. OP
Date: Fri, 30 Nov 2007 10:39:37 +0100 [thread overview]
Message-ID: <8ccc8ba40711300139i61b83aa6o31c658a37a2ecae3@mail.gmail.com> (raw)
In-Reply-To: <20071130084155.GA14203@nibiru.local>
We have a (secret, as usual) plan to implement another version of Op
so that its semantics match styx for files not QTCACHEABLE yet it
could even outperform Op for QTCACHEABLE files. It's still not clear yet
the best way to decorate qids, but we thing we can do it.
That's scheduled after o/mero o/live, which means that I still have to debug
the sam command language for o/live, and that means no one should hold
the breath waiting for this thing to be available.
On Nov 30, 2007 9:41 AM, Enrico Weigelt <weigelt@metux.de> wrote:
>
> Hi folks,
>
> I've read some bit about OP and wonder if 9P could be extended
> to support the new operations from OP transparently if an client
> asks for. This could make the proxy unnecessary in many situations.
>
> cu
> --
> ---------------------------------------------------------------------
> Enrico Weigelt == metux IT service - http://www.metux.de/
> ---------------------------------------------------------------------
> Please visit the OpenSource QM Taskforce:
> http://wiki.metux.de/public/OpenSource_QM_Taskforce
> Patches / Fixes for a lot dozens of packages in dozens of versions:
> http://patches.metux.de/
> ---------------------------------------------------------------------
>
prev parent reply other threads:[~2007-11-30 9:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-30 8:41 Enrico Weigelt
2007-11-30 9:39 ` Francisco J Ballesteros [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=8ccc8ba40711300139i61b83aa6o31c658a37a2ecae3@mail.gmail.com \
--to=nemo@lsub.org \
--cc=9fans@cse.psu.edu \
--cc=weigelt@metux.de \
/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).