Allowed items to use for vortex_conf_get.

Enumerator
VORTEX_SOFT_SOCK_LIMIT 

Gets/sets current soft limit to be used by the library, regarding the number of connections handled.

Soft limit means it is can be moved to hard limit.

To configure this value, use the integer parameter at vortex_conf_set. Example:

1 vortex_conf_set (VORTEX_SOFT_SOCK_LIMIT, 4096, NULL);
VORTEX_HARD_SOCK_LIMIT 

Gets/sets current hard limit to be used by the library, regarding the number of connections handled.

Hard limit means it is not possible to exceed it.

To configure this value, use the integer parameter at vortex_conf_set. Example:

1 vortex_conf_set (VORTEX_HARD_SOCK_LIMIT, 4096, NULL);
VORTEX_LISTENER_BACKLOG 

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:

1 vortex_conf_set (VORTEX_LISTENER_BACKLOG, 64, NULL);
VORTEX_ENFORCE_PROFILES_SUPPORTED 

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.

VORTEX_AUTOMATIC_MIME_HANDLING 

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.
VORTEX_SKIP_THREAD_POOL_WAIT 

Allows to skip thread pool waiting on vortex ctx finalization.

By default, when vortex context is finished by calling vortex_exit_ctx, the function waits for all threads running the in thread pool to finish. However, under some conditions, this may cause a dead-lock problem especially when blocking operations are triggered from threads inside the pool at the time the exit operation happens.

This parameter allows to signal this vortex context to not wait for threads running in the thread pool.

To set the value to make vortex ctx exit to not wait for threads in the pool to finish use:

1 vortex_conf_set (ctx, VORTEX_SKIP_THREAD_POOL_WAIT, axl_true, NULL);