<HTML>
<HEAD>
<TITLE>Re: [Openstack] eventlet weirdness</TITLE>
</HEAD>
<BODY>
<FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>Why has the ship-sailed?<BR>
This is software we are talking about right, there is always a v2 (....X-1) <BR>
;)<BR>
<BR>
On 3/2/12 12:38 PM, "Caitlin Bestler" <<a href="Caitlin.Bestler@nexenta.com">Caitlin.Bestler@nexenta.com</a>> wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>Duncan McGregor wrote:<BR>
<BR>
<BR>
>Like so many things that are aesthetic in nature, the statement above is misleading. Using a callback, event-based, deferred/promise oriented system is hard for *some*. It is far, far easier for >others (myself included).<BR>
<BR>
>It's a matter of perception and personal preference.<BR>
<BR>
I would also agree that coding your application as a series of responses to events can produce code that is easier to understand and debug.<BR>
And that would be a wonderful discussion if we were starting a new project.<BR>
<BR>
But I hope that nobody is suggesting that we rewrite all of OpenStack code away from eventlet pseudo-threading after the fact.<BR>
Personally I think it was the wrong decision, but that ship has already sailed.<BR>
<BR>
With event-response coding it is obvious that you have to partition any one response into segments that do not take so long to<BR>
Execute that they are blocking other events. That remains true when you hide your event-driven model with eventlet pseudo-threading.<BR>
Inserting sleep(0) calls is the most obvious way to break up an overly event handler, given that you've already decided to obfuscate the<BR>
Code to pretend that it is a thread.<BR>
<BR>
<BR>
<BR>
_______________________________________________<BR>
Mailing list: <a href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a><BR>
Post to : <a href="openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><BR>
Unsubscribe : <a href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a><BR>
More help : <a href="https://help.launchpad.net/ListHelp">https://help.launchpad.net/ListHelp</a><BR>
<BR>
</SPAN></FONT></BLOCKQUOTE>
</BODY>
</HTML>