Gets/sets current backlog configuration for listener connections.
Once a listener is activated, the backlog is the number of complete connections (with the finished tcp three-way handshake), that are ready to be accepted by the application. The default value is 5.
Once a listener is activated, and its backlog is configured, it can't be changed. In the case you configure this value, you must set it (vortex_conf_set) after calling to the family of functions to create vortex listeners (vortex_listener_new).
To configure this value, use the integer parameter at vortex_conf_set. Example:
By default, vortex will allow the application layer to request a channel creation using a profile which wasn't adviced by the remote peer.
Though it could be not required, some BEEP peers may want to hide some profiles until some condition is meet.
Because a new BEEP <greeting> can't be sent advising new profiles supported once those conditions are meet, it is required to allow creating channels under profiles that aren't adviced by the remote peer at the first <greetings> exchange.
This is mainly used by Turbulence BEEP application server for its profile path support, which allows to design a policy to be follow while creating channels, selecting some profiles under some conditions.
By default, the value configured is axl_false, that is, allows to create channels under profiles even not adviced.
If configured, makes all messages send via vortex_channel_send_* to automatically add MIME headers configured.
This means that all messages sent will be configured with a CR+LF prefix assuming the application level is sending the MIME body.
See 4.2 Using MIME configuration for data exchanged under Vortex Library for a long explanation. In sort, this function allows to configure if MIME headers should be added or not automatically on each message sent using the family of functions vortex_channel_send_*.
The set of functions that are affected by this configuration are:
Use the following values to configure this feature:
- 1: Enable automatic MIME handling for messages send over any channel that is not configured.
- 2: Disable automatic MIME handling for channels that aren't configured.