Re: beepcore-c and bpc_send()

1. cf., http://beepcore-c.sourceforge.net/bpc_error_allocate.html

2. asynchronous means you can have multiple requests outstanding and that responses are unordered.

/mtr
  ----- Original Message ----- 
  From: Des Smith 
  To: [email protected] 
  Cc: [email protected] 
  Sent: Thursday, August 01, 2002 9:00 AM
  Subject: [Beepcore-c-users] beepcore-c and bpc_send()


  1. 

   

  RFC 3080 describes the format of the Error Message . It has and error code field, where certain error codes are described in section 8 of the RFC3080.

   

  How is the error code sent when using the bpc_send() function from the beepcore-c libraries. The parameters to bpc_send() do not include any code field. What Im looking for is the C equivalent to the Java Message.sendErr(int code, ..) method.

  Must the buffer sent in an error message using bpc_send() be constructed in some 'special' way to include the error code?

   

  2. In documentation describing BEEP it refers to it as an asynchronous protocol. In what sense is it asynchronous? 

   

  Thanks.