[Vortex] pull api + tls, missing connection closed event

KTamas ktamas at balabit.hu
Tue Aug 30 20:36:38 CEST 2011

I realized that the proposed solution is not enough, as in the 
non-auto_tls case is not covered. Maybe the action should be emited by 
vortex_connection_new_empty, although it gets a little tricky around 
there, because it would be issued before the connection is properly 
tlsficated. I don't know how the infinite loop with auto_tls could be 


On 08/30/2011 06:59 PM, KTamas wrote:
> Hi!
> The problem seems to be that when a TLS connection is being initiated, 
> a new VortexConnection is created but the 
> CONNECTION_STAGE_POST_CREATED action is omitted. This action is used 
> by the PULL API to set the close notification callback on connections 
> (vortex_pull_register_close_connection) so it can issue the 
> corresponding event.
> As a workaround, registering manually the 
> vortex_pull_connection_closed on the connection created by TLS, the 
> close event is issued correctly by PULL.
> A solution might be to emit the CONNECTION_STAGE_POST_CREATED action 
> in vortex_connection_actions_notify if an action's result is 2 
> (meaning a new connection is created), but it might cause a problem 
> with auto_tls, which also uses the CONNECTION_STAGE_POST_CREATED to 
> automatically create a new TLS connection. Maybe it should check for 
> tlsficated connections.
> Tamas
> _______________________________________________
> Vortex mailing list
> Vortex at lists.aspl.es
> http://lists.aspl.es/cgi-bin/mailman/listinfo/vortex

More information about the Vortex mailing list