This article was nominated for deletion on 13 January 2018. The result of the discussion was Wrong forum.

This article is rated C-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects:

Computing Low‑importance This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing Low This article has been rated as Low-importance on the project's importance scale.

A member of the category waste management... :) 131.170.90.3 05:51, 17 May 2006 (UTC)Reply

I don't understand. Is it like a chip or the Windows 95 recycling bin? Stovetopcookies 18:18, 16 November 2006 (UTC)Reply

There are both real(ish) bit buckets (chad buckets) and metaphorical bit buckets (like all the places that deleted and/or lost data ends up).

Atlant 18:29, 16 November 2006 (UTC)Reply

A bit bucket is basically an analogy for any place you place data where it no longer is kept track of. For instance when you empty your recycling bin, all the data's headers are erased, hence they are thrown into the bit bucket.) Of course the data itself doesn't disappear until rewritten, it just is very difficult to find without the file headers to say where it is. --Robert Wm "Ruedii" (talk) 03:40, 10 September 2014 (UTC)Reply

As far as I know there is no thing called "Stream.null" in standatd Java APIs. --94.143.240.23 (talk) 22:54, 19 November 2009 (UTC)Reply

There is a recent use of the term "bit bucket" in terms of QoS scheduling. It refers to the count of a specific type of data on a stream, after it is no longer stored. By creating special null pipes or pipe counters, the server or router can count the amount of data exceeding the recommended volume without actually keeping track of the data amount. Hence it can keep a virtual buffer of all the data estimated to be "in the pipe" between the server and the client, as well as being able to regulate burst activity while still keeping a separate limit on steady bandwidth usage. --Robert Wm "Ruedii" (talk) 03:49, 10 September 2014 (UTC)Reply