Hmm, maybe I meant for this to be a user configurable setting, so that async wouldn't block engine if there was a large queue. Not sure, I'll remove it for now.

Mark
Greg Barton wrote:

Nah, yield() not necessary.  The wait() inside of
LinkedBlockingQueue.take() takes care of that.  But
the Thread.sleep(100) limits the CommandExecutor to
only handling, at most, 10 Commands per second.  Just
wondering why that is.

--- Mark Proctor <mproctor@codehaus.org> wrote:

heh, habit :) Hadn't put that much thought into it,
probably for my 
testing purposes, whats better a standard yield() ?

Mark
Greg Barton wrote:

Just looked at it.  Looks good.

Just curious: why the "Thread.sleep(100)" on line

of  org.drools.concurrent.CommandExecutor?

--- Mark Proctor <mproctor@codehaus.org> wrote:

Greg,

Did you checkout what I did with the async apis

in

4.0 MR2, happy I got 
the balance and implementation right?

Mark

---------------------------------------------------------------------

To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

____________________________________________________________________________________You

snooze, you lose. Get messages ASAP with AutoCheck

in the all-new Yahoo! Mail Beta.

http://advision.webevents.yahoo.com/mailbeta/newmail_html.html

  
      
    




       
____________________________________________________________________________________Luggage? GPS? Comic books? 
Check out fitting gifts for grads at Yahoo! Search
http://search.yahoo.com/search?fr=oni_on_mail&p=graduation+gifts&cs=bz