From: Skip Tavakkolian <9nut@9netics.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] The Web9 Project
Date: Sat, 8 Sep 2007 08:45:07 -0700 [thread overview]
Message-ID: <6a98877f0437be7ed76be727ab932c42@9netics.com> (raw)
In-Reply-To: <EE662DC3-5A6C-45BB-8623-A569338F4C46@kix.in>
nice!
for an eyecandy application, you might want to consider integrating
with something like eyeos (eyeos.org) or similar php based systems.
have you compared its performance to webdav?
> Hi,
>
> Following a request for more information on the project, here are a
> few details:
>
> a) PHP bindings to libixp (client-only; server portion currently
> being worked on). I will probably try to get this included as a
> standard module in the PHP distribution.
>
> b) JS9P - Implementation of the 9P protocol in Javascript. You can
> create and parse auth messages, but authentication is not supported
> at a higher level. The library provides methods to only create and
> parse binary 9P messages, since JS doesn't have native networking
> functionality. The actual transport can be done by either using the
> Mozilla JS-XPCOM extensions (see below) - or using XMLHttpRequests -
> (a sample has implemented - visit the Web9 site for more info).
>
> c) "Angled", a firefox extension to read files of a 9P serve right in
> the browser (uses JS9P). For example, typing in ninep://tcp!
> sources.cs.bell-labs.com!564/plan9/LICENSE into the address bar will
> return that file. Text and Images are shown in the browser itself,
> while other binary files trigger a download request. I'm still trying
> to figure out what is the best kind of interface to offer write/
> modify capabilities for the extension is.
>
> The work is a result of the Summer of Code 2007. You can clone the hg
> repository: http://code.kix.in/hg/web9 or view the code at http://
> code.kix.in/projects/web9/browser (there is also a mirror of the code
> at gsoc.cat-v.org)
> I'm also currently working on a pure PHP implementation of 9P,
> scheduled for inclusion at PEAR (pear.php.net) as the Net_9P package.
>
> Regards,
> --
> Anant
next prev parent reply other threads:[~2007-09-08 15:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <EE662DC3-5A6C-45BB-8623-A569338F4C46@kix.in>
2007-09-08 12:39 ` Enrico Weigelt
2007-09-08 19:38 ` Anant Narayanan
2007-09-08 15:45 ` Skip Tavakkolian [this message]
2007-09-08 19:46 ` Anant Narayanan
2007-09-08 20:15 ` Uriel
2007-09-09 3:46 ` Latchesar Ionkov
2007-09-09 9:44 ` Francisco J Ballesteros
2007-09-09 11:55 ` erik quanstrom
2007-09-09 12:03 ` Francisco J Ballesteros
2007-09-09 12:18 ` erik quanstrom
2007-09-09 12:52 ` 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=6a98877f0437be7ed76be727ab932c42@9netics.com \
--to=9nut@9netics.com \
--cc=9fans@cse.psu.edu \
/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).