GNOME Bugzilla – Bug 40798
Provide char * equivalents to public GnomeVFSURI * functions
Last modified: 2008-09-06 19:17:20 UTC
The interface is completely inconsistent about whether a URI is specified by a char * or a GnomeVFSURI * or both. This needs to be cleaned up because otherwise it's hard to use the library. ------- Additional Comments From pavel@eazel.com 2000-05-06 17:47:53 ---- If I recall correctly, Ettore was suggesting having only GnomeVFSURI * APIs. ------- Additional Comments From snickell@stanford.edu 2001-07-23 00:32:43 ---- Taking bugs previously assigned to Pavel, assigning them to myself. Will parse them out at my leisure , but many are GnomeVFS bugs we should look at for 2.0 ------- Additional Comments From mjs@noisehavoc.org 2001-08-26 21:25:21 ---- I think we'd like to go with a "char *" interface only. For a first cut, all the external interfaces could be changed to use strings but GnomeVFSURI could still be used internally and by modules. ------- Additional Comments From darin@bentspoon.com 2001-08-26 21:27:39 ---- If we do this, we should remember to also change lists of GnomeVFSURI * into lists of char * where they show up in the external API. ------- Bug moved to this database by unknown@bugzilla.gnome.org 2001-09-09 21:18 -------
We're going to have to deal with this in later releases (hopefully by adding string-based functions in 2.2 and removing GnomeVFSURI 3.0
Hello, could we get news from this case ? Is this bug still relevant ? thanks
MASS CHANGE VFS. Re-assigning bugs that I currently own in VFS to the proper owner (probably Alex).
I've investigated the public headers (2.10) and found that we're already very good at providing char * functions. The following functions which do not (yet) provide any equivalent which takes char * arguments instead of a GnomeVFSURI. It is a result of a quick header grep and may not be complete. gnome-vfs-async-ops.h (6) ----- GnomeVFSFindDirectoryResult could have a textual equiv. gnome_vfs_async_create_symbolic_link gnome_vfs_async_get_file_info gnome_vfs_async_set_file_info gnome_vfs_async_xfer gnome_vfs_async_find_directory gnome-vfs-file-info.h (1) ----- GnomeVFSGetFileInfoResult could have a textual equiv. gnome-vfs-find-directory.h ----- gnome_vfs_find_directory (1) gnome-vfs-ops.h (2) ----- gnome_vfs_create_symbolic_link gnome_vfs_uri_exists gnome-vfs-utils.h (1) ----- gnome_vfs_get_volume_free_space gnome-vfs-xfer.h (3, all) ----- gnome_vfs_xfer_uri_list, gnome_vfs_xfer_uri, gnome_vfs_xfer_delete_list)
I'd like to point interested parties in the direction of <http://www.gbiv.com/protocols/uri/rfc/rfc3986.html>, in particular, the differences between the official specification of "URI" and what we are calling a URI. I think whatever happens here with GNOME VFS, we should be careful to make a distinction from what is a "URI Reference" (i.e. a reference to a URI) and an actual, full "URI". I picked up some work a while ago and was frankly a little confused by what was going on with these GnomeVFSURI things because my understanding of URIs comes from the specification! Indeed, the original design for VFS predates this specification, but I don't see that as a reason not to pick it up. I'd also like to ask why we would want to replace any use of GnomeVFSURI with char *.
gnome-vfs has been deprecated and superseded by gio/gvfs since GNOME 2.22, hence mass-closing many of the gnome-vfs requests/bug reports. This means that gnome-vfs is NOT actively maintained anymore, however patches are still welcome. If your reported issue is still valid for gio/gvfs, please feel free to file a bug report against glib/gio or gvfs. @Bugzilla mail recipients: query for gnome-vfs-mass-close to get rid of these notification emails all together. General further information: http://en.wikipedia.org/wiki/GVFS Reasons behind this decision are listed at http://www.mail-archive.com/gnome-vfs-list@gnome.org/msg00899.html