Ack and Nack

"Ack" is short for "acknowledge", and "Nack" is short for "negative acknowledge". There are really 3 options for acknowledging a message:

1. Acknowledge: Processed successfully.
2. Nack and requeue: Not processed successfully, but should be requeued on the same queue to be processed again (retry).
3. Nack and discard: Not processed successfully, and should be discarded (to a dead-letter queue if configured or just deleted entirely).

1. In src/internal/pubsub, update your subscribeJSON function's handler parameter to return an "acktype" instead of nothing.
   1. An "acktype" should be one of:
      • Ack
      • NackRequeue
      • NackDiscard
   2. Depending on the returned "acktype", the handler should either call:
      • Ack: ch.ack(msg)
      • NackRequeue: ch.nack(msg, false, true)
      • NackDiscard: ch.nack(msg, false, false)
2. For testing/debugging purposes, add a log statement alongside each Ack/Nack call to indicate which action occurred.
3. Update your client's "move" and "pause" handlers to return an "acktype".
   1. The "pause" handler should always Ack.
   2. The "move" handler should only "Ack" if:
      • The move outcome was "safe"
      • Or, the move outcome was "make war"
   3. The "move" handler should "NackDiscard" if:
      • The move outcome was "same player"
      • Or, the move outcome was anything else

Test the changes by running 2 clients: washington and napoleon. Have washington spawn a couple of units:

spawn americas artillery

Have napoleon spawn a unit:

spawn europe cavalry

Then have washington move a unit into napoleon's territory:

move europe 1

Napoleon's client should "Ack" the message, and Washington's client should "NackDiscard" the message. Make sure your logs reflect that. You can move on when you're satisfied with the results.

You might notice that nothing went to the dead-letter queue. That's because we haven't configured it yet, and that's okay.