On Mon, 7 Jan 2002, Tom Drake wrote:
> Date: Mon, 7 Jan 2002 12:44:23 -0800
> From: Tom Drake <[EMAIL PROTECTED]>
> Reply-To: Tomcat Users List <[EMAIL PROTECTED]>,
> Tom Drake <[EMAIL PROTECTED]>
> To: Tomcat Users List <[EMAIL PROTECTED]>
> Subject: Re: Problem with file URL
>
> Pae:
>
> The term protocol implies that there is a there is a network based
> exchange of information.
>
> In the case of 'file://' URLs, your client software ends up making
> system calls (e.g. open(), read(), close()), no exchange of
> information across a network.
>
> Ah, but what about files on your network drives? you may ask.
> Same thing goes here. Your client software simply makes open,
> read, and close system calls. However, your O/S, under the covers,
> turns these into network exchanges (e.g. NETBIOS, NFS, SMB, Netware, ...)
> However, your client has no knowledge that these files are hosted
> elsewhere. As far as it can tell these 'remote' filesystems are hosted
> locally. Your client is blissfully unaware of any network activity,
> and of the actual protocol used to retrieve the file. The protocol
> used, in this case is determined by the O/S.
>
> Furthermore, consider that:
>
> The http protocol is defined by RFC 2616.
> The ftp protocol (ftp://) is defined by RFC 0959 / STD009
>
> Can anyone tell me where the file:// protocol is defined?
>
See RFC 1738, section 3.10. All the "official" URL protocols are defined
by one of the RFCs.
> The 'file://' protocol specifier, doesn't actually relate to a known
> protocol.
> It is merely a shorthand way of treating local files as URL's.
>
> Hope this is helpful.
>
> Regards,
>
> Tom Drake
>
Craig McClanahan
--
To unsubscribe: <mailto:[EMAIL PROTECTED]>
For additional commands: <mailto:[EMAIL PROTECTED]>
Troubles with the list: <mailto:[EMAIL PROTECTED]>
