Concurrent Stack Assignment

Motivation

We will build a thread-safe implementation of a Stack using synchronized methods.

Background

Implicit Locks

synchronized methods

Code To Implement

ConcurrentStack

To be @ThreadSafe, one must hold intrinsic lock (via synchronized) on the ConcurrentStack instance for each of the methods which read and/or write to mutable data.

class:	ConcurrentStack.java
methods:	constructor push peek pop
package:	stack.concurrent.exercise
source folder:	student/src/main/java

constructor and instance variables

The constructor

public ConcurrentStack(BiFunction<E, Optional<Node<E>>, Node<E>> nodeCreator)

is passed a nodeCreator. The excessive over use of abstraction is in place to help the testing alert you to potential bugs in your code earlier.

Be sure to hang onto the nodeCreator in a final instance variable along with whatever other state you need to implement a mutable thread-safe Stack.

Testing

class:	__ConcurrentStackTestSuite.java
package:	stack.concurrent.exercise
source folder:	testing/src/test/java

Pledge, Acknowledgments, Citations

file:

concurrent-stack-pledge-acknowledgments-citations.txt

More info about the Honor Pledge