Dashboard > RIFE > ... > Upcoming changes > GenericQueryManager cache
RIFE Log In | Sign Up   View a printable version of the current page.
GenericQueryManager cache


Added by JR Boyens, last edited by JR Boyens on May 20, 2004
Labels: 
(None)

  • To speed up repeated queries.
  • Perhaps an MD5 of the RestoreQuery could be used to determine one ResultSet from another.
  • Since the GQM is fully under our control, the caching issue wouldn't be too terrible because if they don't save() anything, then it hasn't changed.

According to some research most of the crypto hashes these days are pretty secure, or at least they are computationally infeasible to break.

Chance of Collision (2 messages with the same hash):

MD5: 1 in 18, 446, 744, 073, 709, 551, 616 chance of collision

SHA-1: 1 in 1, 208, 925, 819, 614, 629, 174, 706, 176 chance of collision
SHA-256: 1 in 340, 282, 366, 920, 938, 463, 463, 374, 607, 431, 768, 211, 456 chance of collision
SHA-384: 1 in 6, 277, 101, 735, 386, 680, 763, 835, 789, 423, 207, 666, 416, 102, 355, 444, 464, 034, 512, 896 chance of collision
SHA-512: 1 in 115, 792, 089, 237, 316, 195, 423, 570, 985, 008, 687, 907, 853, 269, 984, 665, 640, 564, 039, 457, 584, 007, 913, 129, 639, 936 chance of collision

Posted by JR Boyens at May 21, 2004 06:06 | Permalink

For a bit of scope in the case of MD5:

"If you could try 1,000,000 messages per second, it would take 584,942 years to find a collision. (A machine that could try 1,000,000,000 messages per second would take 585 years, on average."

Posted by JR Boyens at May 21, 2004 06:11 | Permalink


Are you enjoying Confluence? Please consider purchasing it today.
Powered by Atlassian Confluence, the Enterprise Wiki. (Version: 2.2.1a Build:#515 May 19, 2006) - Bug/feature request - Contact Administrators