1. 01 Jul, 2016 1 commit
    • Matthias Clasen's avatar
      Add a new gio commandline tool · 9edba4e4
      Matthias Clasen authored
      This command collects the various commandline utilities that
      are currently shipped in gvfs, and unifies them under a single,
      command-style binary.
      The tools just use GIO APIs, so it makes sense for them to live here.
  2. 29 Jun, 2016 3 commits
  3. 22 Jun, 2016 1 commit
  4. 15 Jun, 2016 1 commit
  5. 24 Jan, 2016 1 commit
  6. 18 Jan, 2016 1 commit
    • Philip Withnall's avatar
      gio: Add DTLS interfaces · c3d6934f
      Philip Withnall authored
      Add a new GDtlsConnection interface, plus derived GDtlsClientConnection
      and GDtlsServerConnection interfaces, for implementing Datagram TLS
      support in glib-networking.
      A GDtlsConnection is a GDatagramBased, so may be used as a normal
      datagram socket, wrapping all datagrams from a base GDatagramBased in
      DTLS segments.
      Test cases are included in the implementation in glib-networking.
  7. 10 Jan, 2016 1 commit
  8. 09 Jan, 2016 1 commit
  9. 08 Jan, 2016 1 commit
  10. 13 Oct, 2015 1 commit
  11. 03 Sep, 2015 1 commit
    • Chun-wei Fan's avatar
      Cleanup and Enhance the MSVC Project Generation · 041e7724
      Chun-wei Fan authored
      Make use of the common autotools module that is used to generate the MSVC
      project files from their respective templates so that the main build files
      beccome cleaner, and enhance them in a way that the headers that should be
      installed can be written to the property sheets during 'make dist', so that
      the chances of missing headers for MSVC builds can be greatly reduced.
      Also use this autotools module to fill in the projects for
      glib-compile-schemas and glib-compile-resources.
  12. 01 Sep, 2015 1 commit
  13. 05 Jun, 2015 2 commits
  14. 03 Jun, 2015 1 commit
  15. 20 Mar, 2015 3 commits
    • Chun-wei Fan's avatar
      Win32: Port Directory Monitoring to New GLocalFileMonitor · 671292bb
      Chun-wei Fan authored
      This WIP patch moves the Windows Directory Monitoring code to the new
      GLocalFileMonitor mechanism, and adds file monitoring in the process.
      Progress from previous patch:
      -File renames are now properly supported, but G_FILE_MONITOR_EVENT_MOVED_IN
       and G_FILE_MONITOR_EVENT_MOVED_OUT needs to be investigated, as
       ReadDirectoryChangesW() seems to send FILE_ACTION_REMOVED when a file is
       moved out of a directory.
      -Events are handled for both the long and short (8.3) variants of the
       filenames, and files monitored will report changes when it is changed
       via its short or long filenames.
      Things to be done:
      -Perhaps find out about attribute changes in files in a monitored
       directory; if a file is monitored, attribute changes are correctly
      -Investigate on G_FILE_MONITOR_EVENT_MOVED_OUT,
      -Investigate on the "boredom" algoritm, and see how we can do it on
    • Allison Karlitskaya's avatar
      fen: remove Solaris file monitor support · 21ab660c
      Allison Karlitskaya authored
      This code is unmaintained and we have no way to port it to the new file
      monitoring API.
    • Allison Karlitskaya's avatar
      substantially rework file monitors · 2737ab32
      Allison Karlitskaya authored
      Remove all event merging and dispatch logic from GFileMonitor.  The only
      implementation of GFileMonitor outside of glib is in gvfs and it already
      does these things properly.
      Get rid of GLocalDirectoryMonitor.  We will use a single class,
      GLocalFileMonitor, for both directory and file monitoring.  This will
      prevent every single backend from having to create two objects
      separately (eg: ginotifydirectorymonitor.c and ginotifyfilemonitor.c).
      Introduce GFileMonitorSource as a thread-safe cross-context dispatch
      mechanism.  Put it in GLocalFileMonitor.  All backends will be expected
      to dispatch via the source and not touch the GFileMonitor object at all
      from the worker thread.
      Remove all construct properties from GLocalFileMonitor and remove the
      "context" construct property from GFileMonitor.  All backends must now
      get the information about what file to monitor from the ->start() call
      which is mandatory to implement.
      Remove the implementation of rate limiting in GFileMonitor and add an
      implementation in GLocalFileMonitor.  gvfs never did anything with this
      anyway, but if it wanted to, it would have to implement it for itself.
      This was done in order to get the rate_limit field into the
      GFileMonitorSource so that it could be safely accessed from the worker
      Expose g_local_file_is_remote() internally for NFS detection.
      With the "is_remote" functionality exposed, we can now move all
      functions for creating local file monitors to a proper location in
      Port the inotify backend to adjust to the changes above.  None of the
      other backends are ported yet.  Those will come in future commits.
  16. 06 Mar, 2015 2 commits
    • Paolo Borelli's avatar
      HTTP proxy support · ed4a7429
      Paolo Borelli authored
      Based on code from "WockyHttpProxy" written by Nicolas Dufresne
      and Marc-André Lureau. Initial glib patch by Brian J. Murrell.
    • Chun-wei Fan's avatar
      Windows: Use Standard Networking Functions If Possible · 6fe28eef
      Chun-wei Fan authored
      Currently, the Windows code use Winsock2-specific APIs to try to emulate
      calls such as inet_pton(), inet_ntop() and if_nametoindex(), which may not
      do the job all the time.  On Vista and later, Winsock2 does provide a
      proper implementation for these functions, so we can use them if they exist
      on the system, by querying for them during g_networking_init().  Otherwise,
      we continue to use the original code path for these, in the case of XP and
      Server 2003.
      This enables many of the network-address tests to pass on Windows as a
      result, when the native Winsock2 implementations can be used.
  17. 02 Mar, 2015 1 commit
  18. 17 Feb, 2015 1 commit
  19. 30 Jan, 2015 2 commits
  20. 21 Jan, 2015 1 commit
  21. 05 Dec, 2014 1 commit
  22. 15 Feb, 2014 1 commit
    • Allison Karlitskaya's avatar
      win32: fixup lib.exe invocation · 7cbff954
      Allison Karlitskaya authored
      We have a configure.ac check for lib.exe that attempts to enable
      creation of .lib files for our 5 public libraries.  That has been broken
      for a long time for two reasons:
       1) the Makefiles hardcode 'lib' instead of 'lib.exe'
       2) we dropped generation of .def files quite some time ago (except for
          in gthread where we have the two-symbol file under version control)
      Add new rules for creating .def files from dumpbin.exe (which you should
      have if you have lib.exe) and fix the .lib rules to use lib.exe.
      Add a bit of $(AM_V_GEN) all around, as well.
  23. 19 Nov, 2013 1 commit
  24. 08 Nov, 2013 1 commit
  25. 07 Nov, 2013 2 commits
  26. 28 Oct, 2013 1 commit
  27. 23 Oct, 2013 1 commit
    • Allison Karlitskaya's avatar
      file-info: Add a G_FILE_ATTRIBUTE_THUMBNAIL_IS_VALID attribute · fe706974
      Allison Karlitskaya authored
      This indicates whether the thumbnail (given by G_FILE_ATTRIBUTE_THUMBNAIL_PATH)
      is valid — i.e. to represent the file in its current state. If
      G_FILE_ATTRIBUTE_THUMBNAIL_IS_VALID is FALSE (for a normal _or_ failed
      thumbnail) it means the file has changed since the thumbnail was generated, and
      the thumbnail is out of date.
      Part of checking thumbnail validity (by the spec) involves parsing
      headers out of the thumbnail .png so we include some (small) code to do
      that in a separate file.  We will likely want to copy this code to gvfs
      to do the same for GVfsFile.
      Heavily based on a patch from Philip Withnall <philip.withnall@collabora.co.uk>
      who suggested the feature and designed the API.
  28. 21 Oct, 2013 4 commits
  29. 17 Oct, 2013 1 commit
    • Colin Walters's avatar
      GSubprocess: New class for spawning child processes · 5b48dc40
      Colin Walters authored
      There are a number of nice things this class brings:
      0) Has a race-free termination API on all platforms (on UNIX, calls to
         kill() and waitpid() are coordinated as not to cause problems).
      1) Operates in terms of G{Input,Output}Stream, not file descriptors
      2) Standard GIO-style async API for wait() with cancellation
      3) Makes some simple cases easy, like synchronously spawning a
         process with an argument list
      4) Makes hard cases possible, like asynchronously running a process
         with stdout/stderr merged, output directly to a file path
      Much rewriting and code review from Ryan Lortie <desrt@desrt.ca>