On Thu, 2012-11-29 at 17:39 +0100, Stef Bon wrote:
> 2012/11/29 Myklebust, Trond <Trond.Myklebust@xxxxxxxxxx>:
> > On Thu, 2012-11-29 at 10:22 -0500, simo wrote:
> >> On Thu, 2012-11-29 at 15:49 +0100, Stef Bon wrote:
> >> > 2012/11/29 Myklebust, Trond <Trond.Myklebust@xxxxxxxxxx>:
> >> > >> -----Original Message-----
> >> > >>
> > NFSv4.1 actually has directory notifications which duplicate most of the
> > functionality of dnotify. The question I'm asking is "Why should we do
> > it?", not "can we do it?".
> >
> > Answers like "well Windows and iOS do it" aren't helpful unless they
> > include a description of what Windows and iOS apps use it for that we
> > can't already do on Linux.
> > If the only application is beagle, then Linux has this really helpful
> > utility called "ssh", which allows you to avoid wasting a load of
> > network bandwidth...
>
> No, sure, you should not do anything because others do it. But on the
> other hand, if others do it, why don't you? Better copy a good idea
> than be stubborn for ever.
The idea that "if we build a bridge, they will come to us" is what gave
rise to dnotify, then inotify (nobody came, so let's build a bigger
bridge) and fsnotify (make it a toll bridge). Nobody is using those
interfaces much on local filesystems, so why is adding it to NFS and
CIFS going to be such a game changer?
> And yes there is no such thing as a killer app, but in my opinion it's
> the user experience. It's so much better when your system keeps track
> on shared network resources.
What does it enable us to do that we can't already do? This is precisely
the question that I asked you in the previous email.
--
Trond Myklebust
Linux NFS client maintainer
NetApp
Trond.Myklebust@xxxxxxxxxx
www.netapp.com
��.n��������+%������w��{.n�����{��w��� jg��� �����ݢj����G���� ���j:+v���w�m������w�������h�����٥
