… and what should happen with them.
Thunar consists of three major components: the application itself (Thunar), the file system abstraction layer (ThunarVFS) and the extension layer (Thunarx). The new ones in town are another VFS layer (GIO) and a set of extensions for it that implements various virtual file systems (GVfs).
ThunarVFS is used almost everywhere inside Thunar. All appearances in the code have to be replaced with equivalent (or improved) implementations based on GIO. In order to do that, we first have to collect information about all the ThunarVFS references in the code. Afterwards, we can determine what to do with each reference. This is done on the page ThunarVFS References in Thunar.
There's not much to say about ThunarVFS other than this: it has to die. See ThunarVFS References in Thunar for more information.
Thunarx has a few references to ThunarVFS in
ThunarxFileInfo which have to be replaced
with GIO equivalents. See ThunarVFS References in Thunar for more information.
There is a number of extensions for Thunar, like
Most of them have references to ThunarVFS or rely on ThunarVFS to work (as is the case with thumbnailers which don't support GIO).
thunar-volman uses ThunarVFS everywhere and will have to be ported to GIO as well. See ThunarVFS References in Thunar for more information.
GIO is supposed to replace ThunarVFS inside Thunar and Thunarx.
GVfs won't be used in Thunar directly. It's just a set of GIO extensions that does its job somwehere in the background. However, there are a few problems with GVfs that I'll have to address: