From: Carl Beame (beame@mail1.tinet.ie)
Date: 12/04/98-09:14:59 AM Z
From: Carl Beame <beame@mail1.tinet.ie>
Subject: Re: NFS V4 attributes proposal
Message-Id: <1998Dec04.151527+0000@games>
Date: 04 Dec 1998 15:14:59 +0000
On Fri Dec 04 00:59:38 1998, ampass wrote:
> Mike Eisler wrote:
> >
> > > I'd say that declaring the attribute already presenting in nfs2/3
> > > protocols (like mtime)
> > > as optional creates unnecessary difficulties for a client, while
> the
> >
> > Why?
> >
>
> Because they will need to invent where to take the data required for
> their OS,
> while the problem is already resolved in all existing servers.
>
> > > server have already resolve
> > > the issue (somehow). I'd propose to declare such an attribute as
> >
> > Existing servers might have kludged around an mtime, but should we
> > "level the playing field" and burden new servers?
>
> Will new servers support nfs2/3?
>
> >
> > > mandatory unless there is
> > > no strong reason to do otherwise.
> >
> > Its either a MUST or a SHOULD.
>
> I propose to say MUST for attributes existing in NFS2/NFS3.
> >
If I can inject a note of practicality at the marketing end.
With optional attributes the following scenario could occur:
A Customer has an NFS V4 client and a couple of NFS V4 servers which
support Attribute "X". As it turns out, the client is "broken" and
does not simulate attribute "X" if it is not provided by the server,
but since the servers the customer has support "X" everything is
working perfectly.
So along comes "Beame & Whiteside Software" with their newfangled NFS
server for the PalmOS which does not support "X". Here is the
conversation which would occur between the customer the tech support
department:
Customer: "We have an application which runs on our client "A" and it
was working with our servers, but when we installed your server it
stopped working. Please fix your server."
Tech: "Actually our server is perfect, your client NFS is broken."
Customer: "But the NFS client works with these other NFS servers, it
must be your server which is broken. Fix it or lose the
sale."
Marketing to Tech.: "Can we fix the bug the customer found in our
server?"
Tech: "It is not our problem, it is a client bug!"
Marketing: "I don't care where the problem is, can you make a fix
which gets us this sale?"
Tech: "Yes, we can simulate the attribute."
Marketing: "Do it!"
- Carl
This archive was generated by hypermail 2.1.2 : 03/04/05-01:46:36 AM Z CST