These are standard service management functions. Sometimes it's start()/stop(), open()/close(), create()/destroy(). Which ever works so long as we're consistent.
Alex Karasulu wrote:It's a bit surprising that everything is stored on disk when you do a destroy()... Last time my computer was destroyed, I wish the data were stored on disk at the same time ;)
The method name is fine. It is intended to denote cleanup of resources
needed for the CL.
This in memory CL was a very very simple proof of concept implementation. I
added the code to backup the content of the CL to a file which get's read on
startup to persist changes instead of loosing them. This mimics a real
persistent CL for testing purposes. If you change this then several tests
will begin to fail. The point is any CL should persist change events, even
if this implementation is just a toy.
More seriously, I understand the logic, but using close() instead of destroy() would have been better.