mirrors/pipewire
1
0
Fork 0
mirror of https://gitlab.freedesktop.org/pipewire/pipewire.git synced 2025-11-03 09:01:54 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions
pipewire/pinos/server/client.h

87 lines
2.5 KiB
C
Raw Normal View History

reintroduce channels Bring back the channel object. Making a node and port on the client side was rather awkward because of the async nature of many methods. It feels better to have a specific communication channel object to interface with a server side port. Use port activate/deactivate to start/stop streams Remove links from the ports. We let other objects install a callback on the port to receive and route buffers.
2016-07-20 17:29:34 +02:00
/* Pinos
* Copyright (C) 2015 Wim Taymans <wim.taymans@gmail.com>
*
* This library is free software; you can redistribute it and/or
* modify it under the terms of the GNU Library General Public
* License as published by the Free Software Foundation; either
* version 2 of the License, or (at your option) any later version.
*
* 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
* Library General Public License for more details.
*
* You should have received a copy of the GNU Library General Public
* License along with this library; if not, write to the
* Free Software Foundation, Inc., 51 Franklin St, Fifth Floor,
* Boston, MA 02110-1301, USA.
*/
#ifndef __PINOS_CLIENT_H__
#define __PINOS_CLIENT_H__
WIP change object model
2016-11-14 12:42:00 +01:00
#ifdef __cplusplus
extern "C" {
#endif
reintroduce channels Bring back the channel object. Making a node and port on the client side was rather awkward because of the async nature of many methods. It feels better to have a specific communication channel object to interface with a server side port. Use port activate/deactivate to start/stop streams Remove links from the ports. We let other objects install a callback on the port to receive and route buffers.
2016-07-20 17:29:34 +02:00
Cleanups Hide GDBus from RTKit API Remove register node from dbus API Add signal Add object and register objects in the registry Add some preregistered types to the registry Let the daemon listen to the registry
2016-11-08 18:00:52 +01:00
#define PINOS_CLIENT_URI "http://pinos.org/ns/client"
#define PINOS_CLIENT_PREFIX PINOS_CLIENT_URI "#"
pass the client object around Pass the client object around, it's easier to deal with than the sender id. Fix the ASYNC return check Don't overwrite the fds of a pollitem, instead keep an index of their position in the global fd array.
2016-09-27 16:59:45 +02:00
typedef struct _PinosClient PinosClient;
track client resources
2016-11-15 17:06:09 +01:00
typedef struct _PinosResource PinosResource;
typedef void (*PinosDestroy) (void *object);
pass the client object around Pass the client object around, it's easier to deal with than the sender id. Fix the ASYNC return check Don't overwrite the fds of a pollitem, instead keep an index of their position in the global fd array.
2016-09-27 16:59:45 +02:00
Rework dbus handling Remove the Daemon object and remove all dbus code from the main objects. We can use the signals in a separate module to create and destroy the DBus interfaces. Move the dbus protocol in a module Move the autolink policy to a module
2016-11-16 16:57:47 +01:00
#include <pinos/server/core.h>
pass the client object around Pass the client object around, it's easier to deal with than the sender id. Fix the ASYNC return check Don't overwrite the fds of a pollitem, instead keep an index of their position in the global fd array.
2016-09-27 16:59:45 +02:00
track client resources
2016-11-15 17:06:09 +01:00
struct _PinosResource {
PinosCore *core;
SpaList link;
Rework dbus handling Remove the Daemon object and remove all dbus code from the main objects. We can use the signals in a separate module to create and destroy the DBus interfaces. Move the dbus protocol in a module Move the autolink policy to a module
2016-11-16 16:57:47 +01:00
PinosClient *client;
track client resources
2016-11-15 17:06:09 +01:00
uint32_t id;
uint32_t type;
void *object;
PinosDestroy destroy;
PINOS_SIGNAL (destroy_signal, (PinosListener *listener,
PinosResource *resource));
};
reintroduce channels Bring back the channel object. Making a node and port on the client side was rather awkward because of the async nature of many methods. It feels better to have a specific communication channel object to interface with a server side port. Use port activate/deactivate to start/stop streams Remove links from the ports. We let other objects install a callback on the port to receive and route buffers.
2016-07-20 17:29:34 +02:00
/**
* PinosClient:
*
* Pinos client object class.
*/
struct _PinosClient {
WIP change object model
2016-11-14 12:42:00 +01:00
PinosCore *core;
cleanups Remove hastables, use lists Remove obsolete ringbuffer some small cleanups
2016-11-15 20:12:31 +01:00
SpaList link;
WIP change object model
2016-11-14 12:42:00 +01:00
PinosGlobal *global;
reintroduce channels Bring back the channel object. Making a node and port on the client side was rather awkward because of the async nature of many methods. It feels better to have a specific communication channel object to interface with a server side port. Use port activate/deactivate to start/stop streams Remove links from the ports. We let other objects install a callback on the port to receive and route buffers.
2016-07-20 17:29:34 +02:00
WIP Change object model
2016-11-10 15:42:14 +01:00
PinosProperties *properties;
reintroduce channels Bring back the channel object. Making a node and port on the client side was rather awkward because of the async nature of many methods. It feels better to have a specific communication channel object to interface with a server side port. Use port activate/deactivate to start/stop streams Remove links from the ports. We let other objects install a callback on the port to receive and route buffers.
2016-07-20 17:29:34 +02:00
track client resources
2016-11-15 17:06:09 +01:00
SpaList resource_list;
WIP change object model
2016-11-14 12:42:00 +01:00
PINOS_SIGNAL (destroy_signal, (PinosListener *listener,
PinosClient *client));
WIP Change object model
2016-11-10 15:42:14 +01:00
};
reintroduce channels Bring back the channel object. Making a node and port on the client side was rather awkward because of the async nature of many methods. It feels better to have a specific communication channel object to interface with a server side port. Use port activate/deactivate to start/stop streams Remove links from the ports. We let other objects install a callback on the port to receive and route buffers.
2016-07-20 17:29:34 +02:00
WIP change object model
2016-11-14 12:42:00 +01:00
PinosClient * pinos_client_new (PinosCore *core,
reintroduce channels Bring back the channel object. Making a node and port on the client side was rather awkward because of the async nature of many methods. It feels better to have a specific communication channel object to interface with a server side port. Use port activate/deactivate to start/stop streams Remove links from the ports. We let other objects install a callback on the port to receive and route buffers.
2016-07-20 17:29:34 +02:00
PinosProperties *properties);
track client resources
2016-11-15 17:06:09 +01:00
SpaResult pinos_client_destroy (PinosClient *client);
reintroduce channels Bring back the channel object. Making a node and port on the client side was rather awkward because of the async nature of many methods. It feels better to have a specific communication channel object to interface with a server side port. Use port activate/deactivate to start/stop streams Remove links from the ports. We let other objects install a callback on the port to receive and route buffers.
2016-07-20 17:29:34 +02:00
track client resources
2016-11-15 17:06:09 +01:00
PinosResource * pinos_client_add_resource (PinosClient *client,
uint32_t type,
void *object,
PinosDestroy destroy);
reintroduce channels Bring back the channel object. Making a node and port on the client side was rather awkward because of the async nature of many methods. It feels better to have a specific communication channel object to interface with a server side port. Use port activate/deactivate to start/stop streams Remove links from the ports. We let other objects install a callback on the port to receive and route buffers.
2016-07-20 17:29:34 +02:00
Rework dbus handling Remove the Daemon object and remove all dbus code from the main objects. We can use the signals in a separate module to create and destroy the DBus interfaces. Move the dbus protocol in a module Move the autolink policy to a module
2016-11-16 16:57:47 +01:00
SpaResult pinos_resource_destroy (PinosResource *resource);
WIP change object model
2016-11-14 12:42:00 +01:00
#ifdef __cplusplus
}
#endif
reintroduce channels Bring back the channel object. Making a node and port on the client side was rather awkward because of the async nature of many methods. It feels better to have a specific communication channel object to interface with a server side port. Use port activate/deactivate to start/stop streams Remove links from the ports. We let other objects install a callback on the port to receive and route buffers.
2016-07-20 17:29:34 +02:00
#endif /* __PINOS_CLIENT_H__ */
Reference in a new issue Copy permalink