Caching responses about whoisit

[meeb]

Heh, I'm very open to adding useful features, less so to bloat 😀

Most of project maintenance after the core is built is offering support and saying no to stuff.

[meeb]

Hi, thanks for the issue. I can see why you might want this but typically this sort of caching would be handled within your application directly (stuffing responses from whoisit into redis with a 24 hour key expiry or similar). Is there an implementation reason that this would make more sense to handle in the query library itself?

As far as I'm aware RDAP servers do not have cache control headers at all, there may be some that do implement them but I've never encountered any. I'm not sure they would make much sense for a query API to implement so I would suspect no endpoints have them. The RDAP RFC doesn't discuss caching other than cache busting to work around poorly implemented MITM proxies.

In-memory caching of Python data structures, if you're making tens of thousands of queries, is going to get pretty massive without offloading it to disk or memcached / redis etc. as well.

[mzpqnxow]

Hi, thanks for the issue. I can see why you might want this but typically this sort of caching would be handled within your application directly (stuffing responses from whoisit into redis with a 24 hour key expiry or similar). Is there an implementation reason that this would make more sense to handle in the query library itself?

As far as I'm aware RDAP servers do not have cache control headers at all, there may be some that do implement them but I've never encountered any. I'm not sure they would make much sense for a query API to implement so I would suspect no endpoints have them. The RDAP RFC doesn't discuss caching other than cache busting to work around poorly implemented MITM proxies.

In-memory caching of Python data structures, if you're making tens of thousands of queries, is going to get pretty massive without offloading it to disk or memcached / redis etc. as well.

Fair enough! Can't day I disagree much with your points, appreciate the detailed explanation

I'll close this

Thanks again

[meeb]

No problem, feel free to open issues if you want to discuss features in the future.

[mzpqnxow]

Hi, thanks for the issue. I can see why you might want this but typically this sort of caching would be handled within your application directly (stuffing responses from whoisit into redis with a 24 hour key expiry or similar). Is there an implementation reason that this would make more sense to handle in the query library itself?

Yes, the reason is deeply technical, you see- I would prefer you maintain it rather than me 😊

^-- joking, sort of.. but when you ask directly like that and I have to think about it, I see that may be the honest answer...