MqContextC - create and manage a slave context … More...

Collaboration diagram for MqContextC_SlaveApi_Slave_CC_API:

Functions
MqContextC *	ccmqmsgque::MqContextC::SlaveGetMaster ()
	`C++: MqContextC* ctx.SlaveGetMaster()` → C-API opposite function of MqSlaveGetFilter

MqContextC *	ccmqmsgque::MqContextC::SlaveGet (MQ_SLAVE_ID id)
	`C++: MqContextC* ctx.SlaveGet(MQ_SLAVE_ID id)` → C-API get the slave-context from a master-context …

MqContextC *	ccmqmsgque::MqContextC::SlaveGetFilter ()
	`C++: MqContextC* ctx.SlaveGetFilter()` → C-API get the filter-ctx or the master-ctx …

MqContextC *	ccmqmsgque::MqContextC::SlaveGetProxy (MQ_SLAVE_ID id)
	`C++: MqContextC* ctx.SlaveGetProxy(MQ_SLAVE_ID id)` → C-API on slave return the master and on master return the slave identified by id.

MK_BOOL	ccmqmsgque::MqContextC::SlaveCheck (MQ_SLAVE_ID id) const
	`C++: MK_BOOL ctx.SlaveCheck(MQ_SLAVE_ID id)` → C-API check if slave-id is valid

void	ccmqmsgque::MqContextC::SlaveCreate (MQ_SLAVE_ID id, MqContextC *slave)
	`C++: ctx.SlaveCreate(MQ_SLAVE_ID id, MqContextC* slave)` → C-API create a master/slave link between the master-parent-context and the slave-parent-context …

void	ccmqmsgque::MqContextC::SlaveCreate (MQ_SLAVE_ID id, const MqContextC &slave)
	`C++: ctx.SlaveCreate(MQ_SLAVE_ID id, MqContextC* slave)` → C-API create a master/slave link between the master-parent-context and the slave-parent-context …

void	ccmqmsgque::MqContextC::SlaveDelete (MQ_SLAVE_ID id)
	`C++: ctx.SlaveDelete(MQ_SLAVE_ID id)` → C-API Delete a slave object from a master/slave link identified by id. …

MK_BOOL	ccmqmsgque::MqContextC::SlaveIs () const
	`C++: MK_BOOL ctx.SlaveIs()` → C-API is the context a slave-context ? …

void	ccmqmsgque::MqContextC::SlaveWorker (MQ_SLAVE_ID id, MK_STRN fct="WORKER", MkBufferListC *args=NULL)
	`C++: ctx.SlaveWorker(MQ_SLAVE_ID id, MK_STRN fct = "WORKER", MkBufferListC* args = NULL)` → C-API create a master/slave link using the image of the ctx object self. …

void	ccmqmsgque::MqContextC::SlaveWorker (MK_NUM id, MK_STRN factory, const MkBufferListC &args)
	`C++: ctx.SlaveWorker(MQ_SLAVE_ID id, MK_STRN fct = "WORKER", MkBufferListC* args = NULL)` → C-API create a master/slave link using the image of the ctx object self. …

Detailed Description

MqContextC - create and manage a slave context …

The master-slave-link is used to create a mesh of nodes defined by different parent-context. The master control the slave.

The master-slave-link is used to perform the following tasks:

report error messages from the slave-context to the master-context
to create a slave-child-context if a master-child-context is created
to delete a slave-context if a master-context is deleted

In difference to the client-server-link the master-slave-link connect two independent parent-context in the same process or thread (e.g. node). This leads to the restriction that only the master-context can be a server-context because only one server-context per node is possible.

   node-0   |           node-1/2        |   node-3/4/5
===================================================================

| <- client/server link -> | <- client/server link -> |

             | <-- master/slave link --> |

                           |- client1-0 -|- server3 ...
             |-  server1  -|
             |             |- client1-1 -|- server4 ...
  client0-0 -|
             |-  server2  -|- client1-2 -|- server5 ...

Definition of the "master-context"

the master-context is a parent-context without a child-context available.
the master-context is a client-context or a server-context.
the link between the master-context and the slave-context is done using MqSlaveWorker or MqSlaveCreate

Definition of the "slave-context"

the slave-context is a parent-context without a child-context available.
the slave-context is a client-context.
the slave-context lifetime is controlled by the master-context.
the slave-context report all error-messages to the master-context.
the slave-context is identified by a unique-slave-id starting with 0.
a special form of a slave-context is a worker-context

Definition of the "worker-context"

the worker-context is a slave-context using the image of the master-context self.
the master-context can be a server-context or a client-context.
the worker-context is created using MqSlaveWorker
the worker-context is identified by a unique-slave-id starting with 0.

Definition of the "slave-id"

the slave-id is defined at enum libmqmsgque::MqSlaveE
a slave is identified in his master-context by a slave-id
the slave-id work like a defined well-known-port-number in /etc/services
the slave-id is an integer value with valid values > 0
it is a good practice to plan the usage of your slave-id(s)

slave

slave-id	value	definition
libmqmsgque::MQ_SLAVE_MAX	1024	internal: the maximum slave-id … .
libmqmsgque::MQ_SLAVE_USER	10	internal: start of user-defined-slave-id .
libmqmsgque::MQ_SLAVE_LOOPBACK	0	internal: the loopback-slave-id, (call my own services) .
libmqmsgque::MQ_SLAVE_FILTER	1	internal: the filter-slave-id, (on a master get the filter-slave) .
libmqmsgque::MQ_SLAVE_MASTER	1	internal: the master-slave-id, (on a slave get the master) .
libmqmsgque::MQ_SLAVE_OTHER	1	internal: on the master-ctx get the slave-ctx and on the slave-ctx get the master-ctx .

range

range	definition
0 <= slave-id < libmqmsgque::MQ_SLAVE_MAX	range of valid slave-id's
0 <= slave-id < libmqmsgque::MQ_SLAVE_USER	internale usage
libmqmsgque::MQ_SLAVE_USER <= slave-id < libmqmsgque::MQ_SLAVE_MAX	external usage

Definition of the "LOOPBACK" (0) slave

   client   |           server            |
===========================================

| <--- client/server --->  | <-- loop --> |

            | <------ master/slave -----> |

  client -- | -- server -- | -- client -- #
                   ==             ==      #
                 server -- | -- client -- #

the loopback has always the slave-id = 0 .
the loopback has the same class as the parent, if reflection is not available the MqFactoryInitial is used.
the loopback is used to call a service on the same process or thread.
the loopback is a special filter without an additional process or thread to be started.
the loopback is only internal accessible
the service called by the loopback need the same attention as the service called by the filter, the context of the service is the loopback-context.
the loopback can call MqServiceCreate to create a new link between a service-token and a service-method, by default all services from the master-context (the owner of the loopback) are also accessible by the loopback.
in the service use MqSlaveGetMaster to get the master-context from the loopback-context.

Example from MyLoopServer.cc → create a new loop-server

#include  "LibMqMsgque_cc.hh"

using namespace ccmqmsgque;

// package-item
class MyLoopServer : public MqContextC, public MqServerSetupIF {
  friend class MqFactoryCT<MyLoopServer>;

  // set the "mydata" attribute to the master-context
  MK_STRN mydata = "Hello World";

  // define the factory constructor
  MyLoopServer(MK_TYP const typ, MqContextC* tmpl=NULL) : MqContextC(typ, tmpl) {};

  private:
    // service to serve all EXTERNAL requests for token "HLWO"
    void HLWO_srv () {
      // get the "loopback" context
      auto loop = SlaveGet(MQ_SLAVE_LOOPBACK);
      // call the LOOP service on the SAME server
      loop->Send("W", "LOOP");
      // answer HLWO with string-return from LOOP
      Send("R", "C", loop->ReadSTR());
    }

    // service to serve all INTERNAL requests for token "LOOP"
    void LOOP_srv () {
      // get the "master" context 
      auto master = static_cast<MyLoopServer*>(SlaveGetMaster());
      // answer LOOP with data from MASTER->mydata attribute
      Send("R", "C", master->mydata);
    }

    // define a service as link between the token "HLWO" and the callback "MyFirstService"
    void ServerSetup() {
      // EXTERNAL: link the "HLWO" service with "HLWO_srv"
      ServiceCreate("HLWO", MqServiceICB(&MyLoopServer::HLWO_srv));
      // INTERNAL: link the "LOOP" service with "LOOP_srv"
      SlaveGet(MQ_SLAVE_LOOPBACK)->ServiceCreate("LOOP", MqServiceICB(&MyLoopServer::LOOP_srv));
    }
};

// package-main
int MK_CDECL main(int argc, MK_STRN argv[]) {
  MqMsgque::CcMqSetup();

  // create "MyLoopServer" factory… and the instance
  auto srv = MqFactoryCT<MyLoopServer>::Add("MyLoopServer")->New();

  try {
    srv->LinkCreate( MkBufferListC {argc, argv} );
    srv->ProcessEvent (MQ_WAIT_FOREVER);
  } catch (const std::exception& e) {
    srv->ErrorCatch(e);
  }
  return srv->Exit();
}

Performance analyse

The performance-test is created with:

pipe
- Nhi1Exec perfclient.c --parent --wrk ? @ perfserver.c
spawn, fork, thread
- Nhi1Exec -r=uds perfserver.c --spawn|fork|thread
- Nhi1Exec -r=uds perfclient.c --parent --wrk ?
the number of workers are set with the –wrk option
the cpu is a xeon with 4/8
the performance is calculated as worker-context-created / time-in-sec with a ~2sec (default) measurement period.

performance-test code:

The test-setup is done as:

  perfclient                                worker                            perfserver
  ==========                                ======                            ==========
  |
  |- loop --wrk x
    |- MqSlaveWorker(...)               ->  worker[1] 
    |- MqSend(worker[1],"E","STR0..")   ->  PerfWorker_I160(...)
                                            |- loop endless
                                              |- MqContextCreate(...)
                                              |- MqLinkCreate(...)      <->   MqContextCreate(...)
                                              |- MqContextDelete(...)   <->   MqContextDelete(...)
  |- sleep x sec
  |- loop --wrk x
    |- MqSend(worker[1],"C"..,"END0")   ->  PerfWorker_END0(...)
    |                                       |- stop loop
    |- "callback" - add number to all   <-  |- return #context

Using the worker-code:
// asynchronous call

static enum MkErrorE PerfWorker_STR0( MQ_SERVICE_CALL_ARGS ) {

MK_BFL largv = NULL;

MK_BFL pargv = NULL;

MK_I32 num = MqReadI32_e(mqctx);

pargv = MkBufferListDup(MqReadBFL_e(mqctx));

enum MkErrorE ret = MK_OK;

if (num == -1) num = 999999; // endless

// start test until "doNext" is "false" or "num" exceeds

for (int i=0; doNext && i<num; i++) {

// CREATE the context

MQ_CTX ctx = MqContextCreate(NULL, mqctx);

largv = MkBufferListDup(pargv);

MqLinkCreate_C (ctx, largv) {

MqContextErrorMove(mqctx,ctx);

MqContextDelete(ctx);

goto error;

}

//MqSend(ctx,"E","MARK:C","start");

MkBufferListDelete(largv);

// DELETE the context

MqContextDelete(ctx);

// count the loops

worker_count++;

// give PerfWorker_END0 time to update "doNext"

MqProcessEvent(mqctx, MQ_WAIT_NO, MK_TIMEOUT_DEFAULT);

}

end:

//printV("ret=%i, Delete=%p\n", ret, largv)

MkBufferListDelete(largv);

MkBufferListDelete(pargv);

if (doNext == true) {

// finish the test WITHOUT "END0" -> test on --num, answer required.

MqSend_E(mqctx, "R", "I", worker_count);

}

return ret;

error:

if (doNext == true) {

ret = MkErrorStack_1X(mqctx);

} else {

ret = MkErrorReset_1X(mqctx);

}

goto end;

}

performance-test results:

results generated using the debug environment

setup	–wrk	# worker-context	performance	info
pipe	1	2500	1000	the pipe start a new worker-context with spawn
spawn	1	2500	<1000	same as pipe but use network-protocoll
fork	1	3800	4000	the fork is faster than spawn
thread	1	16500	9000	the thread is faster than fork
pipe	4	8000	4500	the worker scale linear up to number of processors
spawn	4	7600	<4500	-
fork	4	23200	11500	-
thread	4	55500	27500	-
pipe	8	10000	5500	the additional scaling up to the max hyper-threading does not really help
spawn	8	9100	<5500	-
fork	8	23200	11500	-
thread	8	55500	27500	-

The master-slave-link is used to create a mesh of nodes defined by different parent-context. The master control the slave.

The master-slave-link is used to perform the following tasks:

report error messages from the slave-context to the master-context
to create a slave-child-context if a master-child-context is created
to delete a slave-context if a master-context is deleted

In difference to the client-server-link the master-slave-link connect two independent parent-context in the same process or thread (e.g. node). This leads to the restriction that only the master-context can be a server-context because only one server-context per node is possible.

   node-0   |           node-1/2        |   node-3/4/5
===================================================================

| <- client/server link -> | <- client/server link -> |

             | <-- master/slave link --> |

                           |- client1-0 -|- server3 ...
             |-  server1  -|
             |             |- client1-1 -|- server4 ...
  client0-0 -|
             |-  server2  -|- client1-2 -|- server5 ...

Definition of the "master-context"

the master-context is a parent-context without a child-context available.
the master-context is a client-context or a server-context.
the link between the master-context and the slave-context is done using MqSlaveWorker or MqSlaveCreate

Definition of the "slave-context"

the slave-context is a parent-context without a child-context available.
the slave-context is a client-context.
the slave-context lifetime is controlled by the master-context.
the slave-context report all error-messages to the master-context.
the slave-context is identified by a unique-slave-id starting with 0.
a special form of a slave-context is a worker-context

Definition of the "worker-context"

the worker-context is a slave-context using the image of the master-context self.
the master-context can be a server-context or a client-context.
the worker-context is created using MqSlaveWorker
the worker-context is identified by a unique-slave-id starting with 0.

Definition of the "slave-id"

the slave-id is defined at enum libmqmsgque::MqSlaveE
a slave is identified in his master-context by a slave-id
the slave-id work like a defined well-known-port-number in /etc/services
the slave-id is an integer value with valid values > 0
it is a good practice to plan the usage of your slave-id(s)

slave

slave-id	value	definition
libmqmsgque::MQ_SLAVE_MAX	1024	internal: the maximum slave-id … .
libmqmsgque::MQ_SLAVE_USER	10	internal: start of user-defined-slave-id .
libmqmsgque::MQ_SLAVE_LOOPBACK	0	internal: the loopback-slave-id, (call my own services) .
libmqmsgque::MQ_SLAVE_FILTER	1	internal: the filter-slave-id, (on a master get the filter-slave) .
libmqmsgque::MQ_SLAVE_MASTER	1	internal: the master-slave-id, (on a slave get the master) .
libmqmsgque::MQ_SLAVE_OTHER	1	internal: on the master-ctx get the slave-ctx and on the slave-ctx get the master-ctx .

range

range	definition
0 <= slave-id < libmqmsgque::MQ_SLAVE_MAX	range of valid slave-id's
0 <= slave-id < libmqmsgque::MQ_SLAVE_USER	internale usage
libmqmsgque::MQ_SLAVE_USER <= slave-id < libmqmsgque::MQ_SLAVE_MAX	external usage

Definition of the "LOOPBACK" (0) slave

   client   |           server            |
===========================================

| <--- client/server --->  | <-- loop --> |

            | <------ master/slave -----> |

  client -- | -- server -- | -- client -- #
                   ==             ==      #
                 server -- | -- client -- #

the loopback has always the slave-id = 0 .
the loopback has the same class as the parent, if reflection is not available the MqFactoryInitial is used.
the loopback is used to call a service on the same process or thread.
the loopback is a special filter without an additional process or thread to be started.
the loopback is only internal accessible
the service called by the loopback need the same attention as the service called by the filter, the context of the service is the loopback-context.
the loopback can call MqServiceCreate to create a new link between a service-token and a service-method, by default all services from the master-context (the owner of the loopback) are also accessible by the loopback.
in the service use MqSlaveGetMaster to get the master-context from the loopback-context.

Example from MyLoopServer.cc → create a new loop-server

#include  "LibMqMsgque_cc.hh"

using namespace ccmqmsgque;

// package-item
class MyLoopServer : public MqContextC, public MqServerSetupIF {
  friend class MqFactoryCT<MyLoopServer>;

  // set the "mydata" attribute to the master-context
  MK_STRN mydata = "Hello World";

  // define the factory constructor
  MyLoopServer(MK_TYP const typ, MqContextC* tmpl=NULL) : MqContextC(typ, tmpl) {};

  private:
    // service to serve all EXTERNAL requests for token "HLWO"
    void HLWO_srv () {
      // get the "loopback" context
      auto loop = SlaveGet(MQ_SLAVE_LOOPBACK);
      // call the LOOP service on the SAME server
      loop->Send("W", "LOOP");
      // answer HLWO with string-return from LOOP
      Send("R", "C", loop->ReadSTR());
    }

    // service to serve all INTERNAL requests for token "LOOP"
    void LOOP_srv () {
      // get the "master" context 
      auto master = static_cast<MyLoopServer*>(SlaveGetMaster());
      // answer LOOP with data from MASTER->mydata attribute
      Send("R", "C", master->mydata);
    }

    // define a service as link between the token "HLWO" and the callback "MyFirstService"
    void ServerSetup() {
      // EXTERNAL: link the "HLWO" service with "HLWO_srv"
      ServiceCreate("HLWO", MqServiceICB(&MyLoopServer::HLWO_srv));
      // INTERNAL: link the "LOOP" service with "LOOP_srv"
      SlaveGet(MQ_SLAVE_LOOPBACK)->ServiceCreate("LOOP", MqServiceICB(&MyLoopServer::LOOP_srv));
    }
};

// package-main
int MK_CDECL main(int argc, MK_STRN argv[]) {
  MqMsgque::CcMqSetup();

  // create "MyLoopServer" factory… and the instance
  auto srv = MqFactoryCT<MyLoopServer>::Add("MyLoopServer")->New();

  try {
    srv->LinkCreate( MkBufferListC {argc, argv} );
    srv->ProcessEvent (MQ_WAIT_FOREVER);
  } catch (const std::exception& e) {
    srv->ErrorCatch(e);
  }
  return srv->Exit();
}

Performance analyse

The performance-test is created with:

pipe
- Nhi1Exec perfclient.c --parent --wrk ? @ perfserver.c
spawn, fork, thread
- Nhi1Exec -r=uds perfserver.c --spawn|fork|thread
- Nhi1Exec -r=uds perfclient.c --parent --wrk ?
the number of workers are set with the –wrk option
the cpu is a xeon with 4/8
the performance is calculated as worker-context-created / time-in-sec with a ~2sec (default) measurement period.

performance-test code:

The test-setup is done as:

  perfclient                                worker                            perfserver
  ==========                                ======                            ==========
  |
  |- loop --wrk x
    |- MqSlaveWorker(...)               ->  worker[1] 
    |- MqSend(worker[1],"E","STR0..")   ->  PerfWorker_I160(...)
                                            |- loop endless
                                              |- MqContextCreate(...)
                                              |- MqLinkCreate(...)      <->   MqContextCreate(...)
                                              |- MqContextDelete(...)   <->   MqContextDelete(...)
  |- sleep x sec
  |- loop --wrk x
    |- MqSend(worker[1],"C"..,"END0")   ->  PerfWorker_END0(...)
    |                                       |- stop loop
    |- "callback" - add number to all   <-  |- return #context

Using the worker-code:
// asynchronous call

static enum MkErrorE PerfWorker_STR0( MQ_SERVICE_CALL_ARGS ) {

MK_BFL largv = NULL;

MK_BFL pargv = NULL;

MK_I32 num = MqReadI32_e(mqctx);

pargv = MkBufferListDup(MqReadBFL_e(mqctx));

enum MkErrorE ret = MK_OK;

if (num == -1) num = 999999; // endless

// start test until "doNext" is "false" or "num" exceeds

for (int i=0; doNext && i<num; i++) {

// CREATE the context

MQ_CTX ctx = MqContextCreate(NULL, mqctx);

largv = MkBufferListDup(pargv);

MqLinkCreate_C (ctx, largv) {

MqContextErrorMove(mqctx,ctx);

MqContextDelete(ctx);

goto error;

}

//MqSend(ctx,"E","MARK:C","start");

MkBufferListDelete(largv);

// DELETE the context

MqContextDelete(ctx);

// count the loops

worker_count++;

// give PerfWorker_END0 time to update "doNext"

MqProcessEvent(mqctx, MQ_WAIT_NO, MK_TIMEOUT_DEFAULT);

}

end:

//printV("ret=%i, Delete=%p\n", ret, largv)

MkBufferListDelete(largv);

MkBufferListDelete(pargv);

if (doNext == true) {

// finish the test WITHOUT "END0" -> test on --num, answer required.

MqSend_E(mqctx, "R", "I", worker_count);

}

return ret;

error:

if (doNext == true) {

ret = MkErrorStack_1X(mqctx);

} else {

ret = MkErrorReset_1X(mqctx);

}

goto end;

}

performance-test results:

results generated using the debug environment

setup	–wrk	# worker-context	performance	info
pipe	1	2500	1000	the pipe start a new worker-context with spawn
spawn	1	2500	<1000	same as pipe but use network-protocoll
fork	1	3800	4000	the fork is faster than spawn
thread	1	16500	9000	the thread is faster than fork
pipe	4	8000	4500	the worker scale linear up to number of processors
spawn	4	7600	<4500	-
fork	4	23200	11500	-
thread	4	55500	27500	-
pipe	8	10000	5500	the additional scaling up to the max hyper-threading does not really help
spawn	8	9100	<5500	-
fork	8	23200	11500	-
thread	8	55500	27500	-

Function Documentation

◆ SlaveCheck()

MK_BOOL ccmqmsgque::MqContextC::SlaveCheck ( MQ_SLAVE_ID id ) const

inline

C++: MK_BOOL ctx.SlaveCheck(MQ_SLAVE_ID id) → C-API
check if slave-id is valid

Definition at line 2168 of file MqContextC_inline_cc.hh.

                                                             {
    MK_UNUSED auto ctx = getCTXN();
    MK_BOOL __retVal__L = MqSlaveCheck(ctx, id);
    return __retVal__L;
  }

◆ SlaveCreate() [1/2]

void ccmqmsgque::MqContextC::SlaveCreate	(	MQ_SLAVE_ID	id,
		const MqContextC &	slave )

inline

C++: ctx.SlaveCreate(MQ_SLAVE_ID id, MqContextC* slave) → C-API
create a master/slave link between the master-parent-context and the slave-parent-context …

Definition at line 2183 of file MqContextC_inline_cc.hh.

                                                                               {
    MK_UNUSED auto ctx = getCTX();
    const MQ_CTX slave_hdl = MqContextC::getCTX(slave);
    enum MkErrorE errVal = MqSlaveCreate(ctx, id, slave_hdl);
    MkErrorC_Check(ctx, errVal);
  }

◆ SlaveCreate() [2/2]

void ccmqmsgque::MqContextC::SlaveCreate	(	MQ_SLAVE_ID	id,
		MqContextC *	slave )

inline

C++: ctx.SlaveCreate(MQ_SLAVE_ID id, MqContextC* slave) → C-API
create a master/slave link between the master-parent-context and the slave-parent-context …

Definition at line 2175 of file MqContextC_inline_cc.hh.

                                                                         {
    MK_UNUSED auto ctx = getCTX();
    MQ_CTX slave_hdl = MqContextC::getCTX(slave);
    enum MkErrorE errVal = MqSlaveCreate(ctx, id, slave_hdl);
    MkErrorC_Check(ctx, errVal);
  }

◆ SlaveDelete()

void ccmqmsgque::MqContextC::SlaveDelete ( MQ_SLAVE_ID id )

inline

C++: ctx.SlaveDelete(MQ_SLAVE_ID id) → C-API
Delete a slave object from a master/slave link identified by id. …

Definition at line 2191 of file MqContextC_inline_cc.hh.

                                                      {
    MK_UNUSED auto ctx = getCTX();
    enum MkErrorE errVal = MqSlaveDelete(ctx, id);
    MkErrorC_Check(ctx, errVal);
  }

◆ SlaveGet()

MqContextC * ccmqmsgque::MqContextC::SlaveGet ( MQ_SLAVE_ID id )

inline

C++: MqContextC* ctx.SlaveGet(MQ_SLAVE_ID id) → C-API
get the slave-context from a master-context …

Definition at line 2139 of file MqContextC_inline_cc.hh.

                                                          {
    MK_UNUSED auto ctx = getCTX();
    MQ_CTX ctx_out;
    enum MkErrorE errVal = MqSlaveGet(ctx, id, &ctx_out);
    MkErrorC_Check(ctx, errVal);
    return MqContextC::MqContextC_ObjNew(MK_RT_CALL ctx_out);
  }

◆ SlaveGetFilter()

MqContextC * ccmqmsgque::MqContextC::SlaveGetFilter ( )

inline

C++: MqContextC* ctx.SlaveGetFilter() → C-API
get the filter-ctx or the master-ctx …

Definition at line 2148 of file MqContextC_inline_cc.hh.

                                                  {
    MK_UNUSED auto ctx = getCTX();
    MQ_CTX ctx_out;
    enum MkErrorE errVal = MqSlaveGetFilter(ctx, &ctx_out);
    MkErrorC_Check(ctx, errVal);
    return MqContextC::MqContextC_ObjNew(MK_RT_CALL ctx_out);
  }

Here is the caller graph for this function:

◆ SlaveGetMaster()

MqContextC * ccmqmsgque::MqContextC::SlaveGetMaster ( )

inline

C++: MqContextC* ctx.SlaveGetMaster() → C-API
opposite function of MqSlaveGetFilter

Definition at line 2130 of file MqContextC_inline_cc.hh.

                                                  {
    MK_UNUSED auto ctx = getCTX();
    MQ_CTX __retVal__L = MqSlaveGetMaster(ctx);
    return MqContextC::MqContextC_ObjNew(MK_RT_CALL __retVal__L);
  }

Here is the caller graph for this function:

◆ SlaveGetProxy()

MqContextC * ccmqmsgque::MqContextC::SlaveGetProxy ( MQ_SLAVE_ID id )

inline

C++: MqContextC* ctx.SlaveGetProxy(MQ_SLAVE_ID id) → C-API
on slave return the master and on master return the slave identified by id.

Definition at line 2157 of file MqContextC_inline_cc.hh.

                                                               {
    MK_UNUSED auto ctx = getCTX();
    MQ_CTX ctx_out;
    enum MkErrorE errVal = MqSlaveGetProxy(ctx, id, &ctx_out);
    MkErrorC_Check(ctx, errVal);
    return MqContextC::MqContextC_ObjNew(MK_RT_CALL ctx_out);
  }

◆ SlaveIs()

MK_BOOL ccmqmsgque::MqContextC::SlaveIs ( ) const

inline

C++: MK_BOOL ctx.SlaveIs() → C-API
is the context a slave-context ? …

Definition at line 2198 of file MqContextC_inline_cc.hh.

                                            {
    MK_UNUSED auto ctx = getCTXN();
    MK_BOOL __retVal__L = MqSlaveIs(ctx);
    return __retVal__L;
  }

◆ SlaveWorker() [1/2]

void ccmqmsgque::MqContextC::SlaveWorker	(	MK_NUM	id,
		MK_STRN	factory,
		const MkBufferListC &	args )

inline

C++: ctx.SlaveWorker(MQ_SLAVE_ID id, MK_STRN fct = "WORKER", MkBufferListC* args = NULL) → C-API
create a master/slave link using the image of the ctx object self. …

Definition at line 21 of file MqContextC_inline_cc.hh.

                                                                                                   {
    MK_BAC args_hdl = MkBufferListC::getBFL(args);
    MkRtSetup_XN(args_hdl);
    enum MkErrorE errVal = MqSlaveWorker (reinterpret_cast<MQ_CTX>(hdl), id, fct, args_hdl);
    ErrorCheck(errVal);
  }

◆ SlaveWorker() [2/2]

void ccmqmsgque::MqContextC::SlaveWorker	(	MQ_SLAVE_ID	id,
		MK_STRN	fct = "WORKER",
		MkBufferListC *	args = NULL )

inline

C++: ctx.SlaveWorker(MQ_SLAVE_ID id, MK_STRN fct = "WORKER", MkBufferListC* args = NULL) → C-API
create a master/slave link using the image of the ctx object self. …

Definition at line 2205 of file MqContextC_inline_cc.hh.

                                                                                        {
    MK_UNUSED auto ctx = getCTX();
    MK_BAC args_hdl = MkBufferListC::getBFL__null_allow(args);
    enum MkErrorE errVal = MqSlaveWorker(ctx, id, fct, args_hdl);
    MkErrorC_Check(ctx, errVal);
  }

Functions

Detailed Description

Function Documentation

◆ SlaveCheck()

◆ SlaveCreate() [1/2]

◆ SlaveCreate() [2/2]

◆ SlaveDelete()

◆ SlaveGet()

◆ SlaveGetFilter()

◆ SlaveGetMaster()

◆ SlaveGetProxy()

◆ SlaveIs()

◆ SlaveWorker() [1/2]

◆ SlaveWorker() [2/2]