Let me try that again, I've never replied to mailing lists before and I
THINK I am doing it correctly this time.
There doesn't appear to be an official list of asset types supported by
the asset cdn. I know that indra/llcommon/llassettype.cpp defines the
asset type names in LLAssetDictionary::LLAssetDictionary() under "TYPE
NAME", and "CAN FETCH" seems to relate to if it can fetch it over HTTP(I
could be wrong though). At the moment the following seem to supported:
* texture
* sound
* landmark
* clothing
* bodypart
* animatn
* gesture
* mesh
* settings (EEP environment, but is called "Settings blob", so may
have expanded use in the future)
These can also be accessed via this URL format:
http://<cap_url>/<asset_id>.<asset_type>.
Notecards (sadly) appear to be off the table, at least for now,
according to https://jira.secondlife.com/browse/BUG-134114. I'd assume
that will include lsltext. So that leaves:
* callcard - Handled by AIS and not really needed via HTTP. IIRC this
is a meta asset, it just is a pointer to a avatar.
* script - Legacy script, either LSL bytecode(unneeded by viewer) or
LSL text(see why notecards were rejected).
* object - No need for the viewer to download this.
* category - Handled via AIS.
* lslbyte - No need for the viewer to get this unless client side
scripting is added which is unlikely.
* txtr_tga - Unused.
* snd_wav - Unused.
* img_tga - Unused.
* jpeg - Unused.
* simstate - Will likely never ever be sent to the viewer unless in
god mode.
* link - Handled via AIS.
* link_f - Handled via AIS.
* widget - No idea what this is, appears unused. If it is what I think
it is(LSL XUI), it might be supported in the future.
* person - Probably internal agent information, no need for the viewer
to get this.
On 8/11/19 11:30 AM, Cinder Roxley wrote:
Greetings on a pleasant Sunday morning!
I am updating Radegast and LibreMetaverse to support HTTP asset
fetching via ViewerAsset capability.
(https://github.com/cinderblocks/libremetaverse)
I have scoured the wiki for API doc on ViewerAsset, and one does not
exist publicly. I have gotten most of it to work, but I need to know
what exactly is and is NOT supported. It appears textures, mesh,
sound, animations, landmarks, do indeed work, and this seems to cover
the bulk of what was obsoleted and removed.
However, the viewer code would suggest any asset type should be
downloadable, but when I attempt to use the scheme GET
http://<cap_url>/?<asset type>_id=<asset id> notecard, lsltext, and
other asset types return “Invalid Syntax”.
So my question is, what asset types are supported? Is migration to
HTTP ongoing? eg. Will notecards and scripts be moved to the
capability away from UDP? If so, I will simply handle the error code
and fallback. If there’s no plan to move them, I won’t bother with
that and leave fetching on UDP for unsupported types.
_______________________________________________
Policies and (un)subscribe information available here:
http://wiki.secondlife.com/wiki/OpenSource-Dev
Please read the policies before posting to keep unmoderated posting privileges
--
Kyler "Félix" Eastridge
Softhyena.com
78 Princess CT. 42701
Elizabethtown, Kentucky, U.S.A.
_______________________________________________
Policies and (un)subscribe information available here:
http://wiki.secondlife.com/wiki/OpenSource-Dev
Please read the policies before posting to keep unmoderated posting privileges
