Top |
GObject ╰── GInitiallyUnowned ╰── GstObject ╰── GstElement ╰── GstBaseSrc ╰── GstPushSrc ╰── GstSocketSrc
Receive data from a socket.
As compared to other elements:
socketsrc can be considered a source counterpart to the multisocketsink sink.
socketsrc can also be considered a generalization of tcpclientsrc and tcpserversrc: it contains all the logic required to communicate over the socket but none of the logic for creating the sockets/establishing the connection in the first place, allowing the user to accomplish this externally in whatever manner they wish making it applicable to other types of sockets besides TCP.
As compared to fdsrc socketsrc is socket specific and deals with GSocket objects rather than sockets via integer file-descriptors.
see_also
: multisocketsink
plugin |
tcp |
author |
Thomas Vander Stichele <thomas at apestaart dot org>, William Manley <will@williammanley.net> |
class |
Source/Network |
“send-messages”
property“send-messages” gboolean
Control if the source will handle GstNetworkMessage events. The event is a CUSTOM event named 'GstNetworkMessage' and contains:
"buffer", GST_TYPE_BUFFER : the buffer with data to send
The buffer in the event will be sent on the socket. This allows for simple bidirectional communication.
Flags: Read / Write
Default value: FALSE
Since: 1.8.0
“connection-closed-by-peer”
signalvoid user_function (GstSocketSrc *gstsocketsrc, gpointer user_data)
Flags: Run First