Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion Thread blocking vs Future async
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Dong Wang 王东  
View profile  
 More options May 2 2012, 5:38 pm
From: Dong Wang 王东 <dongw.perso...@gmail.com>
Date: Thu, 3 May 2012 05:38:08 +0800
Local: Wed, May 2 2012 5:38 pm
Subject: Re: Thread blocking vs Future async
Thanks James.

~Dong

在 May 3, 2012,4:30 AM,James Waldrop <j...@twitter.com> 写道:

> Given the way you've described it, yes, your db would have 100 connections.

> Sent from my iPhone

> On May 2, 2012, at 12:06 PM, Dong Wang <dongw.perso...@gmail.com> wrote:

>> I have a twitter util.Future based application that needs to read data from DB. I'd like to see 100 concurrent reads from the database using Future, I don't think I need to create a FuturePool with 100 threads but I do need to make sure the db client has at least 100 connections, do I? Thanks.


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.