Re: Thank you for sl_cache!

What happens when HTTP(S) textures are enabled in the client? Does sl_cache still deliver the texture data or does it come from the SL servers?

When I use UDP textures, sl_cache writes:
[99927] RES_CACHE_IMAGE: sended cache = 53e39f4b-23c1-0cae-f23b-d7b56367d93c.1
[99927] RES_CACHE_IMAGE: sended cache = 53e39f4b-23c1-0cae-f23b-d7b56367d93c.3
[99927] RES_CACHE_IMAGE: sended cache = 53e39f4b-23c1-0cae-f23b-d7b56367d93c.2


Yet when I use HTTP textures, sl_cache writes:
[99927] RES_CACHE_IMAGE: sended cache = 53e39f4b-23c1-0cae-f23b-d7b56367d93c
[99927] RES_CACHE_IMAGE: sended cache = a7bb95f2-9866-f403-d68f-edfbae687b24
[99927] RES_CACHE_IMAGE: sended cache = 8ddd8351-282f-1c8a-2d64-d18f47a1be7b
[99927] RES_CACHE_IMAGE: sended cache = c8e27386-3bc2-7a07-e192-4b406456f775

My question is, is sl_cache still working for me as a cache but just not storing the textures all broken up into UDP packets? I'm trying to understand why my network usages seem to be higher with HTTP(S) textures vs. UDP textures. It may be that I'm just getting new complete copies of the textures.

As long as sl_cache is still caching, it's not useless. At least, not to me.