On Fri, Jan 16, 2009 at 9:01 AM, Bobbie wrote:
> 3) My intent wasn't to create a thread for each key, I just needed to
> make sure the keystrokes were posted in order, so I thought this was
> the best way to do it.
Actually, putting each thing to do in a separate thread ensures that you
have no
Bobbie wrote:
> Here are my replies, next to the number I am answering for your post:
>
> 1) Yes, after every keystroke, I can change that if need be to update
> on a timer instead (would that be a better way to do it?)
Most chat applications wait until , or a button click, or
something to indic
Waiting for the threads to join in this case sort of defeats the purpose of
having the threads... but, yea, the LinkedBlockingQueue sounds like the
solution you need. Just wanted to second that...
On Fri, Jan 16, 2009 at 12:01 PM, Bobbie wrote:
>
> > Your code snippet is useful, but since it is
> Your code snippet is useful, but since it is a part of a larger project,
> some of my comments may be completely wrong. So, your patience is requested.
>
> 1. Do I understand your flow correctly -- you are sending an HTTP POST
> after *every keystroke*? After all, onKeyUp() will get called after
Bobbie wrote:
> I am trying to do a real-time chat application (where the Android
> user's text shows up real-time in a web interface running in a browser
> on someon'es PC). Right now I'm having it post the text in a textbox
> using "onKeyUp" and running it in a background thread (using
> "threa
5 matches
Mail list logo
