jack2/windows/JackWinNamedPipeServerNotif...

66 lines
1.9 KiB
C++

/*
Copyright (C) 2004-2006 Grame
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.
This program 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 General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
*/
#include "JackWinNamedPipeServerNotifyChannel.h"
#include "JackError.h"
#include "JackRequest.h"
#include "JackConstants.h"
#include "JackNotification.h"
namespace Jack
{
int JackWinNamedPipeServerNotifyChannel::Open(const char* server_name)
{
if (fRequestPipe.Connect(jack_server_dir, server_name, 0) < 0) {
jack_error("Cannot connect to server pipe");
return -1;
} else {
return 0;
}
}
void JackWinNamedPipeServerNotifyChannel::Close()
{
fRequestPipe.Close();
}
/*
The requirement is that the Notification from RT thread can be delivered... not sure using a pipe is adequate here...
Can the write operation block?
A non blocking write operation should be used : check if write can succeed, and ignore the notification otherwise
(since its mainly used for XRun, ignoring a notification is OK, successive XRun will come...)
*/
void JackWinNamedPipeServerNotifyChannel::Notify(int refnum, int notify, int value)
{
JackClientNotificationRequest req(refnum, notify, value);
if (req.Write(&fRequestPipe) < 0) {
jack_error("Could not write notification ref = %d notify = %d", refnum, notify);
}
}
void JackWinNamedPipeServerNotifyChannel::NotifyQuit()
{
Notify(-1, kQUIT, 0);
}
} // end of namespace