![maptiler request counter maptiler request counter](https://docs.microsoft.com/en-us/iis/extensions/configuring-application-request-routing-arr/using-performance-counters/_static/image3.jpg)
In my case, I encoded state into Base64 representation and stored it as a hash fragment in the URL. With only start and end times to store as state, it was not that crazy to store it as part of the URL (it’s not a lot of data!).
#Maptiler request counter code
Option 2 would have required me to provision a server and database, design a database schema to store the data, write code to write data to and fetch data from the database, as well as maintain API routes to return data to the client. I’m lazy and I want to optimize for results per unit work done.Obviously, I opted for the second option, because: I could encode the state within the URL itself, so each countdown link contains all the state it needs.Creating a countdown would generate a new ID, and loading a countdown link (containing the ID) would retrieve the state. I could store state in a database and identify each countdown by a unique ID.(In this case, the state would include start and end times.) There are a couple of ways I could do this: A bookmarkable countdown must mean that some state is being stored somewhere that is loaded into the application when the countdown link is loaded.
![maptiler request counter maptiler request counter](https://sc01.alicdn.com/kf/HTB152Qec21H3KVjSZFBq6zSMXXaQ/235882908/HTB152Qec21H3KVjSZFBq6zSMXXaQ.jpg)
Right off the top of my head, I had a few ideas for implementing that. The primary engineering design decision I needed to make pertains to the requirement of “bookmarkable and revisitable”. It’s a countdown app - I shouldn’t have to wait too long for it to load. Damn it, I just (primarily) want to see the progress bar and a completion percentage. Some of the sites I found were not user-friendly, requiring multiple dropdown selections for day, month, year, hour, and minute.
![maptiler request counter maptiler request counter](https://i.pinimg.com/736x/ec/ce/94/ecce948fcb1340a9da807734b9f61f47.jpg)
It should be stupidly simple and easy to use.In addition to the above functional requirements, I had a few non-functional requirements: Over the course of the next several days, I hacked together my project, which I call quarantime. I decided to build my own countdown application, which would kill a bunch of time as well. In any case, I didn’t even bother to check for the other 2 requirements. Or perhaps I just wasn’t looking hard enough? This was a surprise to me, because in my mind a visual progress indicator is a completely natural and complementary element in a countdown application to a “time remaining” display. Every offering I found did not provide a progress bar, or any other sort of progress indicator. Perhaps unsurprisingly, I was unable to find any such website.