From: Enrico Weigelt <weigelt@metux.de>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] The Web9 Project
Date: Sat, 8 Sep 2007 14:39:38 +0200 [thread overview]
Message-ID: <20070908123938.GA3661@nibiru.local> (raw)
In-Reply-To: <EE662DC3-5A6C-45BB-8623-A569338F4C46@kix.in>
* Anant Narayanan <anant@kix.in> wrote:
> Following a request for more information on the project, here are a
> few details:
thx :)
> 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.
Cool :)
Do you dock into the stream handling or use separate functions ?
Would be really cool if you simply can fopen() an 9p resource :)
BTW: perhaps you'd noticed I'm working on my own branch of libixp,
called libmixp. It will also contain some address/URI handling
functions, so an individual application doesn't need to care
about this anymore. Maybe you'd like to have a look at it.
> 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).
Huh, tunnel 9p messages through http ?!
> 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.
IMHO, the approach is extending mozilla's stream handling (nsChannel stuff).
Some time ago a had some look at it. Doesn't seem very trivial.
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/
---------------------------------------------------------------------
next parent reply other threads:[~2007-09-08 12:39 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 [this message]
2007-09-08 19:38 ` Anant Narayanan
2007-09-08 15:45 ` Skip Tavakkolian
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=20070908123938.GA3661@nibiru.local \
--to=weigelt@metux.de \
--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).