Robert M. Münch
robert.muench at robertmuench.de
Thu Jan 1 17:48:51 CET 2009
-----BEGIN PGP SIGNED MESSAGE-----
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
-----BEGIN PGP SIGNATURE-----
Version: PGP Desktop 9.9.0 (Build 397)
-----END PGP SIGNATURE-----
More information about the Vortex