Skip to main content
replaced http://stackoverflow.com/ with https://stackoverflow.com/
Source Link

It's a bounded queue (a first-in-first-out queue with a fixed capacity).

This particular queue always allows addition of elements and silently remove head element for newly added element (when full).

In Java there is the CircularFifoQueue that works exactly that way (see also Size-limited queue that holds last N elements in JavaSize-limited queue that holds last N elements in Java).

For .NET you'd take a look at:

It's a bounded queue (a first-in-first-out queue with a fixed capacity).

This particular queue always allows addition of elements and silently remove head element for newly added element (when full).

In Java there is the CircularFifoQueue that works exactly that way (see also Size-limited queue that holds last N elements in Java).

For .NET you'd take a look at:

It's a bounded queue (a first-in-first-out queue with a fixed capacity).

This particular queue always allows addition of elements and silently remove head element for newly added element (when full).

In Java there is the CircularFifoQueue that works exactly that way (see also Size-limited queue that holds last N elements in Java).

For .NET you'd take a look at:

edited body
Source Link
manlio
  • 4.2k
  • 3
  • 26
  • 37

It's a bounded queue (a first-in-first-out queue with a fixed capacity).

This particular queue always allows addition of elements and silently remove head element for newly added element (when full).

In Java there is the CircularFifoQueue that works exactly thisthat way (see also Size-limited queue that holds last N elements in Java).

For .NET you'd take a look at:

It's a bounded queue (a first-in-first-out queue with a fixed capacity).

This particular queue always allows addition of elements and silently remove head element for newly added element (when full).

In Java there is the CircularFifoQueue that works exactly this way (see also Size-limited queue that holds last N elements in Java).

For .NET you'd take a look at:

It's a bounded queue (a first-in-first-out queue with a fixed capacity).

This particular queue always allows addition of elements and silently remove head element for newly added element (when full).

In Java there is the CircularFifoQueue that works exactly that way (see also Size-limited queue that holds last N elements in Java).

For .NET you'd take a look at:

edited body
Source Link
manlio
  • 4.2k
  • 3
  • 26
  • 37

It's a bounded queue (a first-in-first-out queue with a fixed capacity).

This particular queue always allows addition of elements and silently remove head element for newly added element (when full).

In Java there is the CircularFifoQueue that works exactly this way (see also Size-limited queue that holds last N elements in Java).

For .NET you'd take a look at:

It's a bounded queue (a first-in-first-out queue with a fixed capacity).

This particular queue always allows addition of elements and silently remove head element for newly added element (when full).

In Java there is the CircularFifoQueue that works exactly this way (see also Size-limited queue that holds last N elements in Java).

It's a bounded queue (a first-in-first-out queue with a fixed capacity).

This particular queue always allows addition of elements and silently remove head element for newly added element (when full).

In Java there is the CircularFifoQueue that works exactly this way (see also Size-limited queue that holds last N elements in Java).

For .NET you'd take a look at:

edited body
Source Link
manlio
  • 4.2k
  • 3
  • 26
  • 37
Loading
Source Link
manlio
  • 4.2k
  • 3
  • 26
  • 37
Loading