Re: Describing file content: MIME attribute ?

New Message Reply About this list Date view Thread view Subject view Author view Attachment view

From: Guy Harris (guy@netapp.com)
Date: 03/21/97-06:04:29 PM Z 

From: guy@netapp.com (Guy Harris)
Message-Id: <199703220004.QAA12595@tooting.netapp.com>
Subject: Re: Describing file content: MIME attribute ?
Date: 	Fri, 21 Mar 1997 16:04:29 -0800 (PST)

> I only ask that NFS V4 allow for  a standardized mechanism to solve the 
> problem, for it is often a pressing one. If the server who supplies the
> file was kind enough to provide the information, the client and/or a 
> pointer to a broker to help the client access the file, then this would
> be easy.

Easy for the client to interpret the pointer to the broker?  To do that,
you'd need a standardized mechanism to specify such a pointer....

> NFS V4 Server providers would have to work out how they would do
> this,
> and NFS V4 clients must be smart enough to do this, but before all that 
> the protocol must allow for this to happen. (As for Frame Maker, they might
> provide an applet the URL of which the protocol returns; your browser fetches
> the applet and you are home; you are one ahead of the guy who does not even
> know that it is a Frame Maker document).

What if there *isn't* such an applet?  What if your machine is incapable
of running that applet?

New Message Reply About this list Date view Thread view Subject view Author view Attachment view

This archive was generated by hypermail 2.1.2 : 03/04/05-01:45:36 AM Z CST