luc14n0/glib
1
0
Fork 0
mirror of https://gitlab.gnome.org/GNOME/glib.git synced 2024-11-10 11:26:16 +01:00
Code Issues Packages Projects Releases Wiki Activity
6f84f6823b
glib/gio/gioprivate.h

41 lines
1.4 KiB
C
Raw Normal View History

GInputStream: Add g_input_stream_async_read_is_via_threads() 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
2013-02-24 00:32:31 +01:00
/* GIO - GLib Input, Output and Streaming Library
*
* Copyright (C) 2013 Collabora Ltd.
*
* This library is free software; you can redistribute it and/or
* modify it under the terms of the GNU Lesser General Public
* License as published by the Free Software Foundation; either
gio/: LGPLv2+ -> LGPLv2.1+ Sub-directories inside gio/ already processed in a previous commit: - fam/ - gdbus-2.0/ (which contains only codegen/) - gvdb/ - inotify/ - tests/ - win32/ - xdgmime/ Other sub-directories inside gio/: - completion/: no license headers - kqueue/: not LGPL, BSD-style license https://bugzilla.gnome.org/show_bug.cgi?id=776504
2017-05-27 18:21:30 +02:00
* version 2.1 of the License, or (at your option) any later version.
GInputStream: Add g_input_stream_async_read_is_via_threads() 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
2013-02-24 00:32:31 +01:00
*
* This library is distributed in the hope that it will be useful,
* but WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
* Lesser General Public License for more details.
*
* You should have received a copy of the GNU Lesser General
Updated FSF's address
2014-01-23 12:58:29 +01:00
* Public License along with this library; if not, see <http://www.gnu.org/licenses/>.
GInputStream: Add g_input_stream_async_read_is_via_threads() 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
2013-02-24 00:32:31 +01:00
*/
#ifndef __G_IO_PRIVATE_H__
#define __G_IO_PRIVATE_H__
#include "ginputstream.h"
GOutputStream: Add g_output_stream_async_write_is_via_threads() In implementing a better g_output_stream_splice_async() and possibly other situtations it's helpful to know whether the output stream's write function internally uses threads. If it and the input stream's read 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 output stream's g_output_stream_write_async() function internally uses threads. https://bugzilla.gnome.org/show_bug.cgi?id=691581
2013-02-24 00:42:49 +01:00
#include "goutputstream.h"
GSocketClient: For _CONNECTING event, make remote address accessible My application (hotssh) would like to get the resolved address from DNS, before we start the connect(). We could add a new event, but it's easy enough to just cache it on the GSocketConnection; this avoids any new API. https://bugzilla.gnome.org/show_bug.cgi?id=712547
2013-11-18 22:15:34 +01:00
#include "gsocketconnection.h"
#include "gsocketaddress.h"
GInputStream: Add g_input_stream_async_read_is_via_threads() 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
2013-02-24 00:32:31 +01:00
G_BEGIN_DECLS
gboolean g_input_stream_async_read_is_via_threads (GInputStream *stream);
streams: add private 'async close via threads' API Add an internal helper to find out if close_async() is implemented via threads using the default implementation in the base class. We will use this to decide if we should do a 'pure async' close of a GIOStream or not. https://bugzilla.gnome.org/show_bug.cgi?id=741630
2015-01-20 14:09:33 +01:00
gboolean g_input_stream_async_close_is_via_threads (GInputStream *stream);
GOutputStream: Add g_output_stream_async_write_is_via_threads() In implementing a better g_output_stream_splice_async() and possibly other situtations it's helpful to know whether the output stream's write function internally uses threads. If it and the input stream's read 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 output stream's g_output_stream_write_async() function internally uses threads. https://bugzilla.gnome.org/show_bug.cgi?id=691581
2013-02-24 00:42:49 +01:00
gboolean g_output_stream_async_write_is_via_threads (GOutputStream *stream);
streams: add private 'async close via threads' API Add an internal helper to find out if close_async() is implemented via threads using the default implementation in the base class. We will use this to decide if we should do a 'pure async' close of a GIOStream or not. https://bugzilla.gnome.org/show_bug.cgi?id=741630
2015-01-20 14:09:33 +01:00
gboolean g_output_stream_async_close_is_via_threads (GOutputStream *stream);
GInputStream: Add g_input_stream_async_read_is_via_threads() 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
2013-02-24 00:32:31 +01:00
GSocketClient: For _CONNECTING event, make remote address accessible My application (hotssh) would like to get the resolved address from DNS, before we start the connect(). We could add a new event, but it's easy enough to just cache it on the GSocketConnection; this avoids any new API. https://bugzilla.gnome.org/show_bug.cgi?id=712547
2013-11-18 22:15:34 +01:00
void g_socket_connection_set_cached_remote_address (GSocketConnection *connection,
GSocketAddress *address);
GInputStream: Add g_input_stream_async_read_is_via_threads() 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
2013-02-24 00:32:31 +01:00
G_END_DECLS
#endif /* __G_IO_PRIVATE__ */
Reference in New Issue Copy Permalink