🚀 go-pugleaf

Hi

My job is to implement a win32 service with a COM Interface in it.

It allows a COM client connect to my service and input some data ,

invoking an "Issue" method and my service will make a socket connection to a
remote host

send it a message and then wait for reply from remote

after remote reply, my service will return a value to Client.

note that the 'message send' and 'message receive' are in the same connection.

so here is the code...

/****************************************************/

int __fastcall TService1::Issue()
{
  char msg[] = "Some Message here....";
  int   msglen = sizeof(msg);

  try
  {
    ClientSocket1->Active = true;    // initially it is false

    // looping until Active is true
    while( ClientSocket1->Active == false)
ServiceThread->ProcessRequests(false);

    // message sending
    ClientSocket1->Socket->SendBuf( msg, msglen);

    // looping until remote reply
    while( ClientSocket1->Active == true)
ServiceThread->ProcessRequests(false);
  }
  catch( ... )
  {
    ClientSocket1->Active = false;
    return -1;
  }

  return 0;
}

void __fastcall TService1::ClientSocket1Read(TObject *Sender, TCustomWinSocket
*Socket)
{
  char buff[BUFFSIZE];
  int    len;

  len = Socket->ReceiveLength();
  Socket->ReceiveBuf( buff, len);
  ..... // do some processing
}

/****************************************************/

It works OK when only one client at a time, it is goot enough for this job.

but sill wandering whether there is a better way to do this or not

(say looping in COM method instead of Service method ?)

Any suggestion will be appreciate^^

What you've said is true. I should have my program multithreading


"Remy Lebeau (TeamB)" wrote:

> You should not be looping like that to begin with.  What exactly are you
> trying to accomplish in the first place?  Typically, you should be using
> multiple threads instead.  Don't put your work in the service's main thread
> at all, leave that alone to service the incoming SCM requests only.
>
> Gambit