From: "J. Bruce Fields" <bfields@fieldses.org>
To: Rob Gardner <rob.gardner@hp.com>
Cc: "nfs@lists.sourceforge.net" <nfs@lists.sourceforge.net>,
"Fábio Jr." <fjuniorlista@gmail.com>
Subject: Re: [NFS] Export especific file extension
Date: Tue, 28 Jul 2009 12:21:21 -0400 [thread overview]
Message-ID: <20090728162121.GH19497@fieldses.org> (raw)
In-Reply-To: <4A6F2018.1040808@hp.com>
On Tue, Jul 28, 2009 at 09:58:16AM -0600, Rob Gardner wrote:
> You could go into the kernel and hack a filter into say, the nfs lookup
> code, and cause lookup failures for files named '*.jpg' on certain
> exports. That would scale, though would take quite a bit more work.
This sounds more like a problem that should be solved on the application
side....
E.g. surely there's a way to configure apache (or whatever) to map paths
like $foo.jpg to /nfs/image-server/$foo.jpg?
--b.
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that nfs@lists.sourceforge.net is being discontinued.
Please subscribe to linux-nfs@vger.kernel.org instead.
http://vger.kernel.org/vger-lists.html#linux-nfs
prev parent reply other threads:[~2009-07-28 16:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-27 20:31 [NFS] Export especific file extension "Fábio Jr."
2009-07-27 22:20 ` Rob Gardner
2009-07-28 11:06 ` "Fábio Jr."
2009-07-28 13:20 ` Rob Gardner
2009-07-28 13:36 ` "Fábio Jr."
2009-07-28 13:53 ` Rob Gardner
2009-07-28 14:40 ` "Fábio Jr."
2009-07-28 15:58 ` Rob Gardner
2009-07-28 16:21 ` J. Bruce Fields [this message]
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=20090728162121.GH19497@fieldses.org \
--to=bfields@fieldses.org \
--cc=fjuniorlista@gmail.com \
--cc=nfs@lists.sourceforge.net \
--cc=rob.gardner@hp.com \
/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