Hacker News Reader

Nice write up, I am glad that you had such a fulfilling internship and chose to share your experience with us.

In your post you mention working around the browser’s maximum URL length. Assuming this is due to the size of the URL parameters containing “data items”, did you consider POSTing the data instead? Also, could you elaborate more on how your solution is able to reconstruct the query on the backend after reducing the URL length by 50%?

View on HN

Yeah, so I did implement the ability to POST the data. However because there was a need to be able to just share a link with someone and see everything they saw, so I had to somehow fit everything into the URL. I can't really go more in depth without divulging some info on the type of data, sorry!

Perhaps use a short random string or hash instead which is a reference to the saved state? This is preferable for a few reasons.

Sound like you might benefit with being able to save a configuration file and that the whole dashboard might be a bit too complex for using inside a browser ?

> Also, could you elaborate more on how your solution is able to reconstruct the query on the backend after reducing the URL length by 50%?

Seems like it’s for readability on either end so maybe a dictionary is a solution for when it’s actually used

Reply on news.ycombinator.com