[Vortex] vortex_channel_wait_reply deadlocks until vortex_connection_new is called on remote

[Chris Yourch]

I am not being clear here. I have exactly one connection to each peer BUT I was not using the connection object passed to my listener when a new connection was established by a remote peer. I have just finished updating my code so that my connection cache will use the connection passed to the listener.

Many thanks for the insight!

Chris


-----Original Message-----
From: Jens Alfke [mailto:jens at mooseyard.com]
Sent: Monday, May 05, 2008 10:51 AM
To: Chris Yourch
Cc: Vortex
Subject: Re: [Vortex] vortex_channel_wait_reply deadlocks until vortex_connection_new is called on remote


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