Vortex Handlers: Handlers used across Vortex Library for async notifications.

VortexAsyncQueueForeach VortexChannelFrameSize VortexChannelPoolCreate VortexChannelSelector VortexConnectionNew VortexConnectionNotifyNew VortexConnectionOnChannelUpdate VortexConnectionOnClose VortexConnectionOnCloseFull VortexConnectionOnPreRead VortexIoAddToFdGroup VortexIoClearFdGroup VortexIoCreateFdGroup VortexIoDestroyFdGroup VortexIoDispatch VortexIoDispatchFunc VortexIoHaveDispatch VortexIoIsSetFdGroup VortexIoWaitOnFdGroup VortexListenerReady VortexListenerReadyFull VortexLogHandler VortexOnAcceptedConnection VortexOnChannelCreated VortexOnChannelPoolCreated VortexOnCloseChannel VortexOnClosedChannel VortexOnClosedNotification VortexOnClosedNotificationFull VortexOnFrameReceived VortexOnNotifyCloseChannel VortexOnStartChannel VortexOnStartChannelExtended VortexProfileMaskFunc VortexReceiveHandler VortexSaslAuthAnonymous VortexSaslAuthAnonymousFull VortexSaslAuthCramMd5 VortexSaslAuthCramMd5Full VortexSaslAuthDigestMd5 VortexSaslAuthDigestMd5Full VortexSaslAuthExternal VortexSaslAuthExternalFull VortexSaslAuthNotify VortexSaslAuthPlain VortexSaslAuthPlainFull VortexSendHandler VortexTlsAcceptQuery VortexTlsActivation VortexTlsCertificateFileLocator VortexTlsCtxCreation VortexTlsPostCheck VortexTlsPrivateKeyFileLocator VortexTunnelLocationResolver VortexXmlRpcBootNotify VortexXmlRpcServiceDispatch VortexXmlRpcValidateResource XmlRpcInvokeNotify

typedef axl_bool(* VortexOnStartChannelExtended)(char *profile, int channel_num, VortexConnection *connection, char *serverName, char *profile_content, char **profile_content_reply, VortexEncoding encoding, axlPointer user_data) Channel start message received handler with support for extended attributes. In most situations, while using Vortex Library, you can assume the default implementation to handle the start channel request. However, a start message request could have several attributes and additional parameters that are notified in the form of a "piggyback", to set up new channels, performing especial operations, as happens with TLS negotiation. This handler allows to get start message notification with all possible data received. Here is an channel start message example: <start number='1' serverName='my.domain.com'> <profile uri='http://some-unique-profile-uri/mech' encoding='none'> <![CDATA[some necessary initial round trip data]]> </profile> </start> This handler will notify the channel number being requested, the serverName value, the profile requested, the piggyback encoding and the optional piggyback. Keep in mind that the encoding is an implicit attribute. Having it not defined yields to the default value 'none', which is represented by EncodingNone. Functions using this handler: vortex_profiles_register_extended_start Parameters: profile  The profile being request to create a new channel. channel_num  Channel being requested for creation. connection  Connection where the channel creation request was received. serverName  Value for this optional start message attribute. This is used profile_content  Optional profile content received inside the channel start message. profile_content_reply  Optional profile content reply to be used for channel start reply, it will be freed by the library after the reply is sent. encoding  Encoding used for the profile content. user_data  User defined data to be passed in to the handler when it is executed. Returns: axl_true if the new channel can be created or axl_false if not.