[GNOME VFS] gnome_vfs_cancellation

Hi guys,

	I'm somewhat uncertain about the difference between
GnomeVFSCancellation and GnomeVFSContext - why we bother having both of
these, and what the plan is for them ?

	It also strikes me as extremely broken ( and indeed, it's causing major
problems on the big Solaris machines serving Sun Rays )  that we
allocate 2 file descriptors per async operation queued.

	_Especially_ since we don't actually use the file descriptors anywhere.
Ok so we read and write to them like lambs, but they are never polled [
it seems to me ], making them particularly pointless. It seems we rely
on the old "setting/reading booleans across threads is safe" gag - which
in this case is probably fair enough.

	So - I'm going to delay the pipe creation until someone calls _get_fd [
which no-one does AFAICS ], which will save us 2 file descriptors per
context creation, speed up async ops, and get us working again.

	In the long term I'd want to bin GnomeVFSCancellation, and merge it's
functionality into GnomeVFSContext - those two seem somewhat confused [
but perhaps I'm confused - who knows ]. Is there anyone interested in
doing such tedious API cleaning / deprecation ?

	Regards,

		Michael.

-- 
 [email protected]  <><, Pseudo Engineer, itinerant idiot


_______________________________________________
gnome-vfs maillist  -  [email protected]
http://lists.ximian.com/mailman/listinfo/gnome-vfs