I am caching the responses from a commercial API services to save costs. (i.e. 
the code does a lookup on a 4D table on the exact URL of the API call to see if 
we already have that response in the cache).

What is people’s opinion on best practice for storing and querying on URL’s ? 
Should we hash them (say with MD5 Digest or something) in case the URL has 
dodgy characters like back-slashes or @ that might screw up 4D's query algo and 
then search on the hash instead ?

Best Regards


4D Internet Users Group (4D iNUG)
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com

Reply via email to