For CGI endpoints that are called infrequently—daily, weekly, or even monthly—the script startup delay is negligible. Even a persistent process waiting to handle a request can have its memory swapped to disk by the OS under varying server load. When a request finally arrives, the delay from swapping that memory back in can negate any theoretical advantage over a cold-starting CGI script.
My status reports are pretty benign and I keep it generic: "solved a P2 relating to Java GC by allocating more memory" or "created a powerpoint slide deck outlining the benefits of on-prem versus adobe cloud for AEM". Not worth creating a new account.
Technically it's just 128 bits, it doesn't matter how you represent it. I've written this IPv4ES solution, which allows you to use 128 bit addresses using IPv4 format.
