[Vortex] vortex_channel_wait_reply deadlocks until vortex_connection_new is called on remote

[Jens Alfke]

On 5 May '08, at 10:38 AM, Chris Yourch wrote:

> Hmmm.... On the remote, can I use the connection that is passed to  
> my listener instead of calling vortex_connection_new()?

Yes. Connections are bidirectional, and either peer can send messages  
over a channel, or open new channels.

In principle there's no reason to have to open more than one  
connection between any two hosts (at least not by the same  
application.) That's one of of the problems BEEP was explicitly  
designed to solve.

You might want to look for a copy of Marshall Rose's book on BEEP,  
published by O'Reilly; the first half is a good conceptual overview of  
the protocol. (Unfortunately the second half is all about using other  
BEEP APIs, but I think the first half is worth the price of a used  
copy.)

—Jens
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 1875 bytes
Desc: not available
Url : http://lists.aspl.es/pipermail/vortex/attachments/20080505/2e77fb67/attachment.bin