1. 24 Jan, 2016 1 commit
  2. 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.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=752240
      c3d6934f
  3. 10 Jan, 2016 1 commit
  4. 09 Jan, 2016 1 commit
  5. 08 Jan, 2016 1 commit
  6. 13 Oct, 2015 1 commit
  7. 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.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=735429
      041e7724
  8. 01 Sep, 2015 1 commit
  9. 05 Jun, 2015 2 commits
  10. 03 Jun, 2015 1 commit
  11. 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
       handled.
      -Investigate on G_FILE_MONITOR_EVENT_MOVED_OUT,
       G_FILE_MONITOR_EVENT_MOVED_IN, G_FILE_MONITOR_EVENT_PRE_UNMOUNT,
       G_FILE_MONITOR_EVENT_UNMOUNTED.
      -Investigate on the "boredom" algoritm, and see how we can do it on
       Windows.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=730116
      671292bb
    • 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.
      21ab660c
    • 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
      thread.
      
      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
      glocalfilemonitor.c
      
      Port the inotify backend to adjust to the changes above.  None of the
      other backends are ported yet.  Those will come in future commits.
      2737ab32
  12. 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.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=733876
      ed4a7429
    • 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.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=730352
      6fe28eef
  13. 02 Mar, 2015 1 commit
  14. 17 Feb, 2015 1 commit
  15. 30 Jan, 2015 2 commits
  16. 21 Jan, 2015 1 commit
  17. 05 Dec, 2014 1 commit
  18. 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.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=722033
      7cbff954
  19. 19 Nov, 2013 1 commit
  20. 08 Nov, 2013 1 commit
  21. 07 Nov, 2013 2 commits
  22. 28 Oct, 2013 1 commit
  23. 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.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=709898
      fe706974
  24. 21 Oct, 2013 4 commits
  25. 17 Oct, 2013 3 commits
  26. 04 Oct, 2013 1 commit
  27. 29 Sep, 2013 1 commit
    • Mike Ruprecht's avatar
      GInputStream: Add g_input_stream_async_read_is_via_threads() · 94a232a4
      Mike Ruprecht authored
      In implementing a better g_output_stream_splice_async() and possibly
      other situtations it's helpful to know whether the input stream's
      read function internally uses threads. If it and the output stream's
      write async functions use threads, then the splice function could
      spawn a single thread for better efficiency.
      
      This patch adds a function to determine whether an input stream's
      g_input_stream_read_async() function internally uses threads.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=691581
      94a232a4
  28. 28 Sep, 2013 1 commit
  29. 19 Aug, 2013 1 commit