Date: Sun, 18 Mar 2001 12:51:04 -0800 (PST) From: Matt Dillon <dillon@earth.backplane.com> To: "Duncan Barclay" <dmlb@dmlb.org> Cc: "Peter Pentchev" <roam@orbitel.bg>, "Kris Kennaway" <kris@obsecurity.org>, <hackers@FreeBSD.ORG>, <fs@FreeBSD.ORG> Subject: Re: httpfs Message-ID: <200103182051.f2IKp4g01900@earth.backplane.com> References: <20010310031515.A8998@mollari.cthul.hu> <20010315095533.C12432@ringworld.oblivion.bg> <000d01c0ad3c$0ed83fb0$d26020c2@Cadence.COM>
next in thread | previous in thread | raw e-mail | index | archive | help
:I don't really think that portalfs is the right thing to use to build
:an httpfs with, but I would like to see how you managed to get your example
:to work. Are you using stdout to create an anonymous file handle? What happens
:if two processes concurrently read from /p/http/*?
:
:Duncan
:
:--
:_____________________________________________________________
:Duncan Barclay | God smiles upon the little children,
You could certainly write a program to sit in the middle and cache
the request to handle that case.
The problem with portalfs is that you can't 'cd' into it or do
directory operations on it, and filesystem operations such as lseek,
fstat, and so forth cannot be intercepted. It would be the ultimate
coolness if you could.
We need a better solution then faking an NFS mount to be able to run
*real* filesystems in user space.
But, that aside, portalfs works just dandy for getting simple file handles
from a path.
-Matt
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200103182051.f2IKp4g01900>