Note that there are some explanatory texts on larger screens.

plurals
  1. USMunish Goyal
    primarykey
    data
    text
    plurals
    1. COIf there is any std. breakup of which kind of values goes where as pointed by Pierre-Alain. then that would be last bit of info to complete this. Like you brought out resx can be used for strings. Timeouts and other app-wide settings in web.config. Otherwise i think i fairly got the pros cons of all methods now and will be able to decide.
      singulars
    2. COfundamentally thats what the point i was truying to make in my above comments. 256 bit output space and a good algo should ensure rare collisions. Well, i am ok to live with rare collisions (if they cant be avoided), i assume no algo gives guarantee of being collision-free. So its like 32 byte hash for avg 100 byte url. this is imp. decision for me to make up-front, going with 128-bit or 256. Because if we are able to scale well for 100 billion, then we will target even much higher. So a future-proof solution and mitigation startegy needs to be thought somewhat now.
      singulars
    3. COthnx 4 ur valuable advise. Well, its start of our project, so quick storage candidate for me is DB. I assume i just need to create an index over a field (here hash) for fast search and rest of the work will be done by DB. And as an edit, URL avg length as mentioned in research is ~100 bytes. So as such URLs alone would amount to 10 TB leave alone their other accompanying data. that opens up the whole data storage problem for us anyway. But coming to this problem, as you said, SHA256.
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload