Show a cover letter.

GET /api/covers/1490/?format=api
HTTP 200 OK
Allow: GET, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

{
    "id": 1490,
    "url": "https://patchwork.libcamera.org/api/covers/1490/?format=api",
    "web_url": "https://patchwork.libcamera.org/cover/1490/",
    "project": {
        "id": 1,
        "url": "https://patchwork.libcamera.org/api/projects/1/?format=api",
        "name": "libcamera",
        "link_name": "libcamera",
        "list_id": "libcamera_core",
        "list_email": "libcamera-devel@lists.libcamera.org",
        "web_url": "",
        "scm_url": "",
        "webscm_url": ""
    },
    "msgid": "<20190621041519.29689-1-niklas.soderlund@ragnatech.se>",
    "date": "2019-06-21T04:15:17",
    "name": "[libcamera-devel,RFC,0/2] libcamera: ipc: unix: Add a IPC mechanism based on Unix sockets",
    "submitter": {
        "id": 5,
        "url": "https://patchwork.libcamera.org/api/people/5/?format=api",
        "name": "Niklas Söderlund",
        "email": "niklas.soderlund@ragnatech.se"
    },
    "mbox": "https://patchwork.libcamera.org/cover/1490/mbox/",
    "series": [
        {
            "id": 369,
            "url": "https://patchwork.libcamera.org/api/series/369/?format=api",
            "web_url": "https://patchwork.libcamera.org/project/libcamera/list/?series=369",
            "date": "2019-06-21T04:15:17",
            "name": "libcamera: ipc: unix: Add a IPC mechanism based on Unix sockets",
            "version": 1,
            "mbox": "https://patchwork.libcamera.org/series/369/mbox/"
        }
    ],
    "comments": "https://patchwork.libcamera.org/api/covers/1490/comments/",
    "headers": {
        "Return-Path": "<niklas.soderlund@ragnatech.se>",
        "Received": [
            "from bin-mail-out-05.binero.net (bin-mail-out-05.binero.net\n\t[195.74.38.228])\n\tby lancelot.ideasonboard.com (Postfix) with ESMTPS id 7601B61583\n\tfor <libcamera-devel@lists.libcamera.org>;\n\tFri, 21 Jun 2019 06:16:22 +0200 (CEST)",
            "from bismarck.berto.se (unknown [145.14.112.32])\n\tby bin-vsp-out-03.atm.binero.net (Halon) with ESMTPA\n\tid 26e61097-93db-11e9-8601-0050569116f7;\n\tFri, 21 Jun 2019 06:15:16 +0200 (CEST)"
        ],
        "X-Halon-ID": "26e61097-93db-11e9-8601-0050569116f7",
        "Authorized-sender": "niklas@soderlund.pp.se",
        "From": "=?utf-8?q?Niklas_S=C3=B6derlund?= <niklas.soderlund@ragnatech.se>",
        "To": "libcamera-devel@lists.libcamera.org",
        "Date": "Fri, 21 Jun 2019 06:15:17 +0200",
        "Message-Id": "<20190621041519.29689-1-niklas.soderlund@ragnatech.se>",
        "X-Mailer": "git-send-email 2.21.0",
        "MIME-Version": "1.0",
        "Content-Type": "text/plain; charset=UTF-8",
        "Content-Transfer-Encoding": "8bit",
        "Subject": "[libcamera-devel] [RFC 0/2] libcamera: ipc: unix: Add a IPC\n\tmechanism based on Unix sockets",
        "X-BeenThere": "libcamera-devel@lists.libcamera.org",
        "X-Mailman-Version": "2.1.23",
        "Precedence": "list",
        "List-Id": "<libcamera-devel.lists.libcamera.org>",
        "List-Unsubscribe": "<https://lists.libcamera.org/options/libcamera-devel>,\n\t<mailto:libcamera-devel-request@lists.libcamera.org?subject=unsubscribe>",
        "List-Archive": "<https://lists.libcamera.org/pipermail/libcamera-devel/>",
        "List-Post": "<mailto:libcamera-devel@lists.libcamera.org>",
        "List-Help": "<mailto:libcamera-devel-request@lists.libcamera.org?subject=help>",
        "List-Subscribe": "<https://lists.libcamera.org/listinfo/libcamera-devel>,\n\t<mailto:libcamera-devel-request@lists.libcamera.org?subject=subscribe>",
        "X-List-Received-Date": "Fri, 21 Jun 2019 04:16:22 -0000"
    },
    "content": "Hello,\n\nThis is an RFC for how IPC could be implemented using Unix Sockets. It \nsupports transferring data and multiple file descriptors in both \ndirections and in the same message.\n\nAs this is an RFC I'm mostly interested to check if my idea of IPC \nmatches that of Laurent and Paul who are dealing with the IPA API and \nprocess manager. For this reason I have not tried profile the code as it \nwill be in our hot-path or written much (any) Doxygen documentation.\n\nI'm not super happy with the interface towards the user having to resize \nthe vector and then memcpy() to the buffer. Maybe I can think of a more \nneat way to do that. On the whole it feels a bit wrong to use the vector \nas I do, but it provides a nice memory safe way to deal with the \nproblem. Once we start to use this and profile it maybe we could improve \nit if needed. Or if anyone have a neat idea on how to make this nicer \nI'm all ears!\n\nNiklas Söderlund (2):\n  libcamera: ipc: unix: Add a IPC mechanism based on Unix sockets\n  test: ipc: unix: Add test for IPCUnixSocket\n\n src/libcamera/include/ipc_unixsocket.h |  58 +++++\n src/libcamera/ipc_unixsocket.cpp       | 330 +++++++++++++++++++++++++\n src/libcamera/meson.build              |   2 +\n test/ipc/meson.build                   |  20 ++\n test/ipc/unixsocket-slave.cpp          |  92 +++++++\n test/ipc/unixsocket.cpp                | 200 +++++++++++++++\n test/ipc/unixsocket.h                  |  27 ++\n test/meson.build                       |   1 +\n 8 files changed, 730 insertions(+)\n create mode 100644 src/libcamera/include/ipc_unixsocket.h\n create mode 100644 src/libcamera/ipc_unixsocket.cpp\n create mode 100644 test/ipc/meson.build\n create mode 100644 test/ipc/unixsocket-slave.cpp\n create mode 100644 test/ipc/unixsocket.cpp\n create mode 100644 test/ipc/unixsocket.h"
}