From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Sat, 8 Sep 2007 14:39:38 +0200 From: Enrico Weigelt To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu> Subject: Re: [9fans] The Web9 Project Message-ID: <20070908123938.GA3661@nibiru.local> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i Topicbox-Message-UUID: bb6295a8-ead2-11e9-9d60-3106f5b1d025 * Anant Narayanan 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/ ---------------------------------------------------------------------