openstack team mailing list archive
-
openstack team
-
Mailing list archive
-
Message #08301
Re: eventlet weirdness
> an rpc implementation that writes to disk and returns,
A what? I'm not sure what problem you're looking to solve here or what you think the RPC mechanism should do. Perhaps you're speaking of a Kombu or AMQP specific improvement?
There is no absolute need for persistence or durability in RPC. I've done quite a bit of analysis of this requirement and it simply isn't necessary. There is some need in AMQP for this due to implementation-specific issues, but not necessarily unsolvable. However, these problems simply do not exist for all RPC implementations...
--
Eric Windisch
Follow ups
References
-
eventlet weirdness
From: Yun Mao, 2012-02-29
-
Re: eventlet weirdness
From: Johannes Erdfelt, 2012-02-29
-
Re: eventlet weirdness
From: Yun Mao, 2012-03-01
-
Re: eventlet weirdness
From: Johannes Erdfelt, 2012-03-01
-
Re: eventlet weirdness
From: Yun Mao, 2012-03-01
-
Re: eventlet weirdness
From: Adam Young, 2012-03-01
-
Re: eventlet weirdness
From: Brian Lamar, 2012-03-01
-
Re: eventlet weirdness
From: Day, Phil, 2012-03-02
-
Re: eventlet weirdness
From: Jay Pipes, 2012-03-02
-
Re: eventlet weirdness
From: Monsyne Dragon, 2012-03-02
-
Re: eventlet weirdness
From: Kapil Thangavelu, 2012-03-03
-
Re: eventlet weirdness
From: Mark Washenberger, 2012-03-05