[Fiware-miwi] Tundra AssetAPI and XML3D asset system

[Jonne Nauha]

Here is my initial writeup on the Tundra AssetAPI and the asset system in
general. Should list all the relevant interfaces and how they tie together.

Let me know if you want more clarification on something. There is lots of
pseudo-code that i tried to keep as simple as possible while still
conveying the intent of the interfaces. They do now map 1:1 to the current
Tundra implementation but should capture the idea for you.

https://forge.fi-ware.eu/plugins/mediawiki/wiki/miwi/index.php/RealXtend_AssetAPI

This is essentially what we now have with our current WebTundra prototype.
So if I could just plug-in my storage/provider implementation somehow to
XML3D it would be great. At the same time you would not need to start
implementing complex asset providers and can leave that to the app
developer. Ofc your basic HTTP provider should be there always but it
should be possible to replace it with a custom impl.

I think this would make XML3D more generic in terms of how it loads assets
and extend its capabilities further. Not sure how big of an development
effort this is, surely we can also fork XML3D and see if we can implement
it in a way that you would accept that code to upstream.

Best regards,
Jonne Nauha
Meshmoon developer at Adminotech Ltd.
www.meshmoon.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-miwi/attachments/20130906/ff275418/attachment.html>