Yes thanks, that is what I was looking for. I have copied some code and
pasted it below, to show what I am going to try. I’ve also highlighted
the two areas that I could still use some help with. •
*MPD_LOCAL_SOCKET_ADDRESS: *I believe linux SS command should show this.
$ ss -x -a
Kurt,
I am new to socket programming. I will review and get back to you.
Thanks,
Ed
On 8/11/2017 5:19 PM, Kurt Van Dijck wrote:
I am trying to allow a second application to send a STOP command to
MPD, using the existing local socket created by MPD. I would like to
allow a form of
>I am trying to allow a second application to send a STOP command to
>MPD, using the existing local socket created by MPD. I would like to
>allow a form of Convenience Switching. So if music is playing through
>MPD from an MPD client (JRiver). The second application could then
>
>
> On 2017/08/11 20:30, Kurt Van Dijck wrote:
> > Even more nitpicking:
> > mkfifo testfifo
> > echo hello world > testfifo
> > ... wait ...
> > cat testfifo
> > now echo has completed.
>
> This has nothing to do with buffering or writes, because a write
> hasn't happened at this point. It
On 2017/08/11 20:30, Kurt Van Dijck wrote:
> Even more nitpicking:
> mkfifo testfifo
> echo hello world > testfifo
> ... wait ...
> cat testfifo
> now echo has completed.
This has nothing to do with buffering or writes, because a write
hasn't happened at this point. It doesn't block at wri
See Response below
On 8/11/2017 11:05 AM, Max Kellermann wrote:
On 2017/08/11 13:45, ed mcmurray wrote:
On the MPD side I'm not so sure where in the code that I should create,
bind, listen and accept connections, for the socket.
That code already exists. Why do you believe a change to MPD is
Max,
No advantage of using pipes, it was only chosen because of my
unfamiliarity with MPD and sockets.
So now, the second application (running on same computer) will run the
client side of the socket. I know where to create, initiate connection
and write to the socket.
On the MPD side I'm n
>
> On 2017/08/11 13:54, Kurt Van Dijck wrote:
> > in order to successfully write() to a fifo, the read() must
> > complete.
>
> Nitpicking: that part is not true. Linux has a pipe buffer as well,
> which defaults to 64 kB (configurable). Maybe other kernels don't
> have one, but Linux does.
On 2017/08/11 13:54, Kurt Van Dijck wrote:
> in order to successfully write() to a fifo, the read() must
> complete.
Nitpicking: that part is not true. Linux has a pipe buffer as well,
which defaults to 64 kB (configurable). Maybe other kernels don't
have one, but Linux does.
__
On 2017/08/11 13:45, ed mcmurray wrote:
> On the MPD side I'm not so sure where in the code that I should create,
> bind, listen and accept connections, for the socket.
That code already exists. Why do you believe a change to MPD is
necessary?
> I'm sure this should be more obvious, but any hel
> On 2017/08/10 17:35, ed mcmurray wrote:
> > From within the MPD application, I would like to access a Linux Named Pipe
> > FIFO that has been created in a second application. The second application
> > would place a STOP command into the Name Pipe, when appropriate. I would
> > like to insert
On 2017/08/10 17:35, ed mcmurray wrote:
> From within the MPD application, I would like to access a Linux Named Pipe
> FIFO that has been created in a second application. The second application
> would place a STOP command into the Name Pipe, when appropriate. I would
> like to insert code in M
Hi,
From within the MPD application, I would like to access a Linux Named
Pipe FIFO that has been created in a second application. The second
application would place a STOP command into the Name Pipe, when
appropriate. I would like to insert code in MPD to then monitor this
Named Pipe for
13 matches
Mail list logo
