Re: GVfs status report
- From: Alexander Larsson <alexl redhat com>
- To: Dominic Lachowicz <domlachowicz gmail com>
- Cc: gnome-vfs <gnome-vfs-list gnome org>, gtk-devel-list <gtk-devel-list gnome org>, Havoc Pennington <hp redhat com>
- Subject: Re: GVfs status report
- Date: Fri, 14 Sep 2007 14:59:27 +0200
On Fri, 2007-09-14 at 08:16 -0400, Dominic Lachowicz wrote:
> Hi Alex,
> On 9/14/07, Alexander Larsson <alexl redhat com> wrote:
> > On Thu, 2007-09-13 at 14:12 -0400, Havoc Pennington wrote:
> > > Hi,
> > >
> > > There's a lot of code to absorb here, a minor comment, I might expect
> > > GUnixFileInputStream/GWindowsFileInputStream rather than
> > > GLocalFileInputStream.
> > Well, the same class is used on both unix and windows. Its the
> > implementation of "native files", and I don't see any need to split it
> > out really. What differences would there be between the two?
> Well, we'd probably want at least a Win32 implementation in terms of
> the native Windows file API. Windows limits the number of FILE*s or
> fd_ts to 2048 per process. The only way to get around this limitation
> is to use the native API.
Thats mainly a problem with the input streams, but most of the GFile
operations are things like rename, copy, move, etc.
However, it seems that it might make sense for
GLocalFileInput/OutputStream to have special implementations on windows.
] [Thread Prev