ProfessorProfessorAny movement on this? I have another use case where caching within LM would be very helpful -- API result caching. Cisco has an API to lookup vulnerabilities based on platform and version. They also have daily call limits. There is no reason to call on the same platform/version more than once per day, but the "LM way" would be to setup something akin to the MS Patch DS @Mike Suding wrote, so this needs to be bound to AD per host. I can hack around the issue by writing files, but it already bugs me that module scripts can even write files to begin with. Actually doing it makes me remember how dangerous that is and it makes me sad. Having an integrated cache system like this would also allow all collectors in the cache group to leverage the data rather than each caching separately (and increasing the API use rate). Other relevant places API result caching would be useful is for weather lookups for a location -- this only needs to be done once per location every so often (30 minutes perhaps). Not every device in a location needs to actually look up the weather for its location, but you want it to look like that so each device has the status bound. And those services have limits (and costs for increasing limits). Maybe redis is not the specific solution, but something to achieve this would be very helpful.
