Re: codec - thread safe

2007-10-08 Thread David J. Biesack
reasonable size and submit a FutureTask to run the encode or decode, and then do a future.get() when the value is needed. You might even get some concurrency if you can start the encode, then continue doing other work until you need the result. -- David J. Biesack SAS Institute Inc. (919) 531-7771

Re: codec - thread safe

2007-10-08 Thread David J. Biesack
Date: Mon, 8 Oct 2007 16:23:59 +0200 From: =?iso-8859-1?Q?J=F6rg_Schaible?= [EMAIL PROTECTED] David J. Biesack wrote on Monday, October 08, 2007 3:02 PM: Date: Sat, 6 Oct 2007 23:31:19 -0500 From: Qingtian Wang [EMAIL PROTECTED] Well, it's pick-your-poison kind of a deal. Either

Re: codec - thread safe

2007-10-08 Thread David J. Biesack
components on it ;-) Agreed; I, like you, was merely suggesting to what Commons consumers might do to deal with non-threadsafe codecs. - Jörg -- David J. Biesack SAS Institute Inc. (919) 531-7771 SAS Campus Drive http://www.sas.com Cary, NC 27513