[Bug 739546] New: Add new element socketsrc, base class for tcpclientsrc and tcpserversrc

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=739546
  GStreamer | gst-plugins-base | git

           Summary: Add new element socketsrc, base class for tcpclientsrc
                    and tcpserversrc
    Classification: Platform
           Product: GStreamer
           Version: git
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: gst-plugins-base
        AssignedTo: gstreamer-bugs at lists.freedesktop.org
        ReportedBy: gnome at williammanley.net
         QAContact: gstreamer-bugs at lists.freedesktop.org
     GNOME version: ---


Created an attachment (id=289861)
 View: https://bugzilla.gnome.org/attachment.cgi?id=289861
 Review: https://bugzilla.gnome.org/review?bug=739546&attachment=289861

gst-plugins-base: patch: tcp: Add element socketsrc

`socketsrc` can be considered a source counterpart to `multisocketsink`. It can
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. 
The user is responsible for providing the already connected socket and they may
accomplish this in whatever manner they wish.  In particular this makes it
applicable to other types of sockets besides TCP such as UNIX domain sockets.

There are also patches to refactor tcpclientsrc and tcpserversrc in terms of
socketsrc to reduce code-duplication.

These patches build on-top of the tests introduced in #739544.

This will be useful to have a src to add socket-specific functionality to,
specifically the ability to populate the metadata from the GstNet package.

This was written to support my aims of zero-copy video IPC discussed in
#737316, but I believe the patches stand on their own.

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.