Re: [Hamlib-developer] Moving rig_cache out of rig_state into private storage

[Mikael N. <mik...@fa...>]

Hi!

Writing down my 2 cents here, as I've developed parts of the caching code (+ UDP packet updates when cached data changes, incl. waterfall data streaming).

The rig_cache struct and everything related to caching should indeed be completely internal to Hamlib. It's great to have the public API of Hamlib cleaned up.

73,
Mikael OH3BHX

On Sat, May 17, 2025, at 19:45, George Baltz wrote:
> On 5/17/25 4:44 AM, Daniele Forsi wrote:
>> Hello,
>>
>>> I think the rig_cache structure should be completely internal to Hamlib, and not visible to the calling application.
>> that's a good thing
>
>                 ^
>
>              very
>
>>
>>> I hope there's no big use of this data elsewhere.
>> how external software would be using the current cache API?
> Strange are the ways of application programmers
>>
>> I grepped for "rig_cache" in the sources that I have locally (mostly
>> from Debian) and I found it only in Hamlib
>>
>> I searched on github for
>> language:C symbol:rig_cache NOT (path:rig.h OR path:cache.h OR path:cache.c)
>>
>> and found 15 results unrelated to Hamlib; a search that doesn't
>> exclude the files above returns more than 3000 results, including
>> various copies of Hamlib
>
> Given that there were no other responses, I'll go ahead and finish 
> tidying up the code, and create a PR for master.
>
>
>
>
> _______________________________________________
> Hamlib-developer mailing list
> Ham...@li...
> https://lists.sourceforge.net/lists/listinfo/hamlib-developer