_PULSE_CODE_COIDDEATH/_PULSE_CODE_DISCONNECT?

I have a Photon app that receives data from a non-photon app. Is there
anyway the photon app can tell when the non photon app terminates or closes
the connection? The photon app registers a message handler for all messages
but it fails to receive the death/disconnect pulses. Am I doing something
wrong or is this just a limitation?

In the Photon App:
{
// establish channel id
chid = PhChannelAttach( 0, -1 , NULL );

// add msg handler
PtAppAddInput( NULL, 0, MyMsgHandler, NULL );

// pass chid to non-photon app
// enter main loop
}

In non Photon App
{
// get Photon app nid, pid, chid
coid = ConnectAttach( photonAppNid, photonAppPid, photonAppChid,
_NOT_SIDE_CHANNEL, 0 );

// talk to Photon app
// die
}

Brown, Richard brownr_aecl_ca@127.0.0.1 wrote:

I have a Photon app that receives data from a non-photon app. Is there
anyway the photon app can tell when the non photon app terminates or closes
the connection? The photon app registers a message handler for all messages
but it fails to receive the death/disconnect pulses. Am I doing something
wrong or is this just a limitation?

It’s a limitation. The Photon library receives those pulses, but only
cares about the ones that match an existing PtConnectionClient or
PtConnectionServer. There’s no way for you to plug in your own handler
at the moment.