void vortex_channel_set_complete_flag VortexChannel channel,
gboolean  value
 

Allows to set complete frames flag.

BEEP protocol defines that an application level message must be splitted into pieces equal to or less than the channel window size. Those pieces are called frames.

This enable BEEP peers to avoid receiving large messages and other problems relationed with channel starvation. As a consequence, while receiving a message reply, represented by a RPY, ANS or NUL frame type, it could be splitted into several frames.

If you don't want to handle frames segments and then join them back into a single message you can set the complete flag. Once activated, Vortex will join all frames into a single message and deliver it to the application level using the default application delivery defined (second and first level handlers or wait reply method).

By default, every channel created have the complete flag activated.

To clarify:

       -----------------
      |    App level    | Sends a message
       -----------------
      |    A message    | Which is splitted into
       -----------------
      | Several frames  | that frames are sent..
       -----------------
      |  Over a channel |
       -----------------
              ||
              ||
       -----------------
      |  Over a channel | 
       -----------------
      | Several Frames  | are received from remote peer side..
       -----------------
      |    A message    | joined into a single message
       -----------------
      |   App level     | App level receive a complete message
       -----------------

Parameters:
channel the channel to configure.
value TRUE activate complete flag, FALSE deactivates it.