Re: Proposed nsIFile and nsILocalFile Changes - MUST READ

[Doug Turner]

> Given that some of the things which are done only on local, disk based files
> (hence the reason for nsILocalFile in addition to nsIFile) have been moved
> into the File System service, what's left in nsILocalFile becomes so small.
> Do we still need the distinction between the two?
>

I think that we always will want to have a nsILocalFile, even if it is empty
(contains no functions).  The reason is that you will want to know if the file
exists on your local machine.  For this, you can simply QI for this interface.
Adding another attribute (onLocalFS) to EVERY impl of nsIFile which return false
for all but the nsILocalFile impl seams wrong.