Open Stack

On 03/31/2014 04:41 PM, Doug Hellmann wrote:
>
>
>
> On Mon, Mar 31, 2014 at 11:36 AM, Gordon Sim <gsim at redhat.com
> <mailto:gsim at redhat.com>> wrote:
>
>     On 03/31/2014 04:11 PM, Doug Hellmann wrote:
>
>         On Mon, Mar 31, 2014 at 8:54 AM, Gordon Sim <gsim at redhat.com
>         <mailto:gsim at redhat.com>
>         <mailto:gsim at redhat.com <mailto:gsim at redhat.com>>> wrote:
>              Another slight annoyance from the testing pov is that the API
>              provides no way of determining when a server is 'ready'
>         i.e. when
>              its subscriptions are in place. I had to work around this
>         for qpid
>              and rabbit with a short sleep, which is always a bit nasty.
>
>
>         Are you saying that creating the subscription doesn't block
>         until it is
>         ready?
>
>
>     With the blocking executor, if I call start() on the server returned
>     by get_rpc_server(), then the start call blocks (until it detects
>     stop has been called). It does look like this is just an issue for
>     that executor though, since the eventlet executor will return after
>     the listen has been issued.
>
>
> That's how I would expect them to work. Is the eventlet executor not
> "ready" then?

Yes, as I said (in a rather clumsy way), it is just an issue for the 
blocking executor.