On Sun, 22 Jun 2008 21:50:13 -0700, Daniel Pitts
<newsgroup.spamfilter@[EMAIL PROTECTED]
> wrote, quoted or indirectly
quoted someone who said :
>Double Buffering generally refers to rendering, not look-ahead caching,
>which is what you seem to be describing.
The use of the term "double buffering" for lookahead i/o goes back to
the 1960s. Back then the closest you had to rendering was vector
display hardware, where a cathode ray beam traced out an image,
looking like star constellation map.
The buffering you get in BufferedInputStreams uses a single buffer.
That means your thread blocks to do i/o when the buffer empties.
With double buffering rendering, you write to a buffer in RAM.
Periodically, it gets copied to the physical REGEN hardware. If the
copy were done by a video processor, your task would have to block for
this process, analogously to the way disk i/o single buffering works..
If the copy were done by the CPU, your task would not block. It would
simple busy itself with the copy.
--
Roedy Green Canadian Mind Products
The Java Glossary
http://mindprod.com
|
