Dear all,
I am looking at the Second Life client code and wondering the difference between OUT_FULL and OUT_FULL_COMPRESSED.
Both of these are related to ObjectUpdate* messages.
I understand that an object message with OUT_FULL_COMPRESSED needs to be uncompressed first using zlib.
I have found that OUT_FULL_COMPESSED is related to object cache (.slc files).
Therefore, I guess OUT_FULL_CACHED and OUT_FULL_COMPRESSED are closely related.
What I don't know is why there is a objectUpdate message with OUT_FULL.
1) Is there any client UI where we can create and specify that object as OUT_FULL type without compressing it?
If it is the case, why do they want not to compress it?
2) I see that the object sent using OUT_FULL will not be saved in the local cache files.
I understand this is a good policy if the object is really an avatar (LL_PCODE_LEGACY_AVATAR) because an avatar always moves.
What if the object is some general object such as LL_PCODE_VOLUME?
Why does it make sense not to save in the cache in this case?
Any help or links to the answers will be greatly appreciated.
Thank you.