From: Anant Narayanan <anant@kix.in>
To: weigelt@metux.de,
Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] The Web9 Project
Date: Sun, 9 Sep 2007 01:08:41 +0530 [thread overview]
Message-ID: <4213FDC1-61CD-4A86-A293-1840CC1F6017@kix.in> (raw)
In-Reply-To: <20070908123938.GA3661@nibiru.local>
> Do you dock into the stream handling or use separate functions ?
> Would be really cool if you simply can fopen() an 9p resource :)
Right now it's just two classes IxpClient and IxpServer; but thanks
for the suggestion. Making a stream handler for 9P would definitely
be worth it.
> Huh, tunnel 9p messages through http ?!
Yes. Using Mozilla's XPCOM extensions isn't a very portable solution,
and part of the reason web developers choose Javascript is because it
is browser-agnostic. The way this works is that the client encodes a
series of 9P T-messages into a XMLHttpRequest and the script on the
server forwards those messages in-order to the actual 9P service, and
responds with a series of R-messages (which the client can then decode).
> 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.
Yes, an nsIChannel implementation was required for this to work.
Nothing in Mozilla is trivial - but I will admit that I took longer
to learn libdraw than Mozilla's netlib ;)
--
Anant
next prev parent reply other threads:[~2007-09-08 19:38 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 [this message]
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=4213FDC1-61CD-4A86-A293-1840CC1F6017@kix.in \
--to=anant@kix.in \
--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).