Add support for an endpoint that streams AND increments.

[JasonLovesDoggo]

i.e. /stream but it incr's initally.

/stream/hit? (if it's possible)

[thatonecodes]

While stream/hit is technically possible, I'm not sure how RESTful it would be, as the endpoint would need to both modify state + stream updates.
However, if we were to implement this, I would think an endpoint as such:

func StreamAndHitView(c *gin.Context) {
    // Increment first, but don't return response
    IncrementCounter(c)
    
    // Add brief delay to ensure increment propagates
    time.Sleep(100 * time.Millisecond)
    
    // Then stream
    StreamValueView(c)
}

Currently, there is the option of having the client make 2 sequential calls:

// First increment
fetch('https://abacus.jasoncameron.dev/hit/test/counter')
  .then(() => {
    // Then listen for updates
    const sse = new EventSource('https://abacus.jasoncameron.dev/stream/test/counter')
    sse.onmessage = (event) => {
      const data = JSON.parse(event.data)
      console.log('Live value:', data.value)
    }
  })

[JasonLovesDoggo]

Nononoo you never want to use time.sleep in production code! The value would propagate immediately anyways so you wouldn't need it.

And two separate API calls is unnecessarily wasteful considering that most of the CPU cycles involved with a request are in the HTTP processing. Go has some pretty high allocation mime readers