pipewire/src/modules/module-protocol-native/connection.h

97 lines
2.9 KiB
C
Raw Normal View History

/* PipeWire */
/* SPDX-FileCopyrightText: Copyright © 2018 Wim Taymans */
/* SPDX-License-Identifier: MIT */
2017-05-23 19:15:33 +02:00
#ifndef PIPEWIRE_PROTOCOL_NATIVE_CONNECTION_H
#define PIPEWIRE_PROTOCOL_NATIVE_CONNECTION_H
2017-05-23 19:15:33 +02:00
#include <spa/utils/defs.h>
#include <spa/utils/hook.h>
#include <pipewire/extensions/protocol-native.h>
#define MAX_DICT 1024
#define MAX_PARAM_INFO 128
#define MAX_PERMISSIONS 4096
#ifdef __cplusplus
extern "C" {
#endif
struct pw_protocol_native_connection_events {
#define PW_VERSION_PROTOCOL_NATIVE_CONNECTION_EVENTS 0
uint32_t version;
void (*destroy) (void *data);
2017-11-13 11:32:06 +01:00
void (*error) (void *data, int error);
void (*need_flush) (void *data);
protocol: add v0 compatibility For flatpaks we need to be able to support older v0 protocol clients. To handle this we have: - the connection detects an old client when it receives the first message. It can do this by checking the sequence number, on old versions it contains the message size and is never 0, on new clients the sequence number is 0. - We add a new signal at the start of the connection with the detected version number. This installs the right version of the core proxy. We also move the binding of the client until the hello message is received. This way we can have a new client connect (portal), hand over the connection to an old client, which then removes the client binding again in the hello request with a v0 version. There are some changes to the passing of fds in v0 vs v3 which need to investigated some more. - bump version of our interfaces to 3. This makes it possible to have v0 and v3 protocol marshal functions. - Add version number in the proxy. This is mostly automatically done internally based on the version numbers the library is compiled with. Where the version number was in the API before, it is now actually used to look up the right protocol marshal functions. For Proxies there is usually just 1 version, the current one. It is the server that will support different versions. - Add v0 compat marshal functions to convert from and to v0 format. This has some complications. v0 has a type map it keeps in sync with the server. For this we have a static type map with mappings to our own v3 types. Pods are mostly the same except for objects that used to have arbitrary pods in v0 vs spa_pod_prop in v3. Also convert between v0 spa_pod_prop and v3 spa_pod_choice. Formats and commands are also slightly different so handle those mappings as well. We only have marshal functions for the server side (resource) v0 functions. - Add v0 compatible client-node again. It's a bit tricky to map, v0 client-node basically lets the server to the mixing and teeing and just does the processing of the internal node.
2019-10-08 22:52:25 +02:00
void (*start) (void *data, uint32_t version);
};
2017-05-23 19:15:33 +02:00
/** \class pw_protocol_native_connection
2017-05-30 19:46:51 +02:00
*
* \brief Manages the connection between client and server
*
* The \ref pw_protocol_native_connection handles the connection between client
2017-05-30 19:46:51 +02:00
* and server on a given socket.
*/
struct pw_protocol_native_connection {
2017-05-30 19:46:51 +02:00
int fd; /**< the socket */
2017-05-23 19:15:33 +02:00
struct spa_hook_list listener_list;
2017-05-23 19:15:33 +02:00
};
static inline void
pw_protocol_native_connection_add_listener(struct pw_protocol_native_connection *conn,
struct spa_hook *listener,
const struct pw_protocol_native_connection_events *events,
void *data)
{
spa_hook_list_append(&conn->listener_list, listener, events, data);
}
struct pw_protocol_native_connection *
pw_protocol_native_connection_new(struct pw_context *context, int fd);
2017-05-26 08:05:01 +02:00
int pw_protocol_native_connection_set_fd(struct pw_protocol_native_connection *conn, int fd);
2017-05-26 08:05:01 +02:00
void
pw_protocol_native_connection_destroy(struct pw_protocol_native_connection *conn);
2017-05-26 08:05:01 +02:00
int
pw_protocol_native_connection_get_next(struct pw_protocol_native_connection *conn,
const struct pw_protocol_native_message **msg);
2017-05-26 08:05:01 +02:00
uint32_t pw_protocol_native_connection_add_fd(struct pw_protocol_native_connection *conn, int fd);
int pw_protocol_native_connection_get_fd(struct pw_protocol_native_connection *conn, uint32_t index);
2017-05-26 08:05:01 +02:00
struct spa_pod_builder *
pw_protocol_native_connection_begin(struct pw_protocol_native_connection *conn,
uint32_t id, uint8_t opcode,
struct pw_protocol_native_message **msg);
int
pw_protocol_native_connection_end(struct pw_protocol_native_connection *conn,
struct spa_pod_builder *builder);
2017-05-26 08:05:01 +02:00
2018-04-19 20:03:52 +02:00
int
pw_protocol_native_connection_flush(struct pw_protocol_native_connection *conn);
2017-05-26 08:05:01 +02:00
2018-04-19 20:03:52 +02:00
int
pw_protocol_native_connection_clear(struct pw_protocol_native_connection *conn);
2017-05-23 19:15:33 +02:00
void pw_protocol_native_connection_enter(struct pw_protocol_native_connection *conn);
void pw_protocol_native_connection_leave(struct pw_protocol_native_connection *conn);
struct spa_pod *pw_protocol_native_connection_get_footer(struct pw_protocol_native_connection *conn,
const struct pw_protocol_native_message *msg);
2017-05-23 19:15:33 +02:00
#ifdef __cplusplus
} /* extern "C" */
#endif
#endif /* PIPEWIRE_PROTOCOL_NATIVE_CONNECTION_H */