From: Tim Panton westhawk!thp@relay.NL.net
Subject: 9P as a network filesystem protocol
Date: Thu, 11 Jul 1996 20:17:19 +0200 [thread overview]
Message-ID: <19960711181719.OEnPOZNA2jUyaZDAruLwdlsECBldrDZWUiD1L7NmmTM@z> (raw)
I was wondering about using 9P as a protocol for a project that
is un-related to Plan9 itself. It just seems sensible to use
an existing network filesystem protocol rather than trying
to make a new one. I want to export Mailboxes (and other things)
to remote Java applets.
Would anyone care to express an opinion on the status of the
9P protocol - is it copyright for example ?
Would I have a problem if I:
1) implemented a 9P client in (say) Java,
based on the public documenation in the book and
on the 9P manual page.
2) used u9fs to test it.
3) implemented a simple 9P server in Java
4) Used 1) and 3) in a commercial project.
I guess what I'm asking is: is 9P an 'open' specification ?
Thanks for your attention.
- By the way, if anyone has any hints about what to avoid
when implementing 9P I'd love to hear them.
Thanks.
Tim.
next reply other threads:[~1996-07-11 18:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-07-11 18:17 Tim [this message]
1996-07-13 3:59 dmr
1996-07-13 4:11 dmr
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=19960711181719.OEnPOZNA2jUyaZDAruLwdlsECBldrDZWUiD1L7NmmTM@z \
--to=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).