[Vortex] vortex_connection_set_receive_handler

[Robert M. Münch]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA384

Am 01.01.2009, 16:16 Uhr, schrieb Robert M. Münch <robert.muench at robertmuench.de>:

> 4. I thought that a profile is used to put application semantics to a  
> channel. TLS is more like a wrapper for normal BEEP communication. Am I  
> right that when using TLS, first there is a TLS-ified connection made,  
> than the normal BEEP protocol is tunneld through this TLS connection? Or  
> is the TLS property only attached to specific channels?

To clarify this one: For using the vortex_connection_set_receive_handler etc. functions one already need a VortexConnection object. But to get such a object I need to make a connection to a server. What if this server is not a BEEP one (because I need to go through some special proxy)? How can I get an empty, not-connected VortexConnection object where I can set the handlers and than start the whole BEEP stuff?

I ready about vortex_connection_new_empty which just requires a connected socket. I could provide such a socket but Vortex won't be able to do anything with it before I set the receive/send handler. So, why does vortex need this socket information? Just for cleanup?

- -- 
Robert M. Münch
Management and IT freelancer
http://www.robertmuench.de

-----BEGIN PGP SIGNATURE-----
Version: PGP Desktop 9.9.0 (Build 397)
Charset: utf-8

wsBVAwUBSVzz83SQa/BbHGLwAQnnOgf+PwYnWleMeKq3TXjQ6wBBT3izCG3MFmjR
WHPdIP5WXCseHJ7bbldqk+YTfxqghcdSwBtIQNdAtbn7kVw6ToNOoRoD9mWAQI9p
GtaJspYWMJ6gfTOH++6sTs+s1WM3YaDXsEbptwMH6Wpy08qEdVibn+mnKjaAEs42
lZxVyCGO/OYL3+5RrHwvX1mvEutL9AfuDOH3AIbASOybE1970xO3gYtRZODbT+aa
U1/B8BASyXu5ywUTvoOU/sQW2uSo5Bt2MkqnPAK/vOGIYrU+iMshaVON7GIsgvpF
0tfwrWjQ+X86rf3VprD3qP5b53aHtCRPmRtRuCHbiNncWePxQqNgRg==
=tHPJ
-----END PGP SIGNATURE-----