feat: adding httpResolver #20
Conversation
- added httpAsset resolver that while resolving the first asset with an http path, will save that baseUrl and search for assets relative to that path. Calls are made in JS through EM_JS calls, and using -sASYNCIFY allows this call to JS to be synchronous from the C++ side.
| // This path is chosen because if an asset is found with the path /../../../ it will go up the tmp directory structure | ||
| // in the case of using /tmp/ then all relative paths greater than depth 1, will look the same. using 6 here is arbitrary, | ||
| // is there a way to make this always work? | ||
| setBaseTempDir(tempDir.generic_string() + "/1/1/1/1/1/1/"); |
There was a problem hiding this comment.
What's the right way to handle this? Originally I was saving the base asset in the base tmp dir (something like /tmp/baseAsset.usda). However, when assets reference other assets in parent folders (something like ../../../../materials/red.usda, it seems correct to make sure to save that asset in the virtual file system at the same relative place to the original base asset. Here I've arbitrarily created 6 folders called '1' just to allow for up to 6 directories above the root asset. Is there a good way to make this generic? Am I missing something?
| void setBaseTempDir(const std::string &tempDir) const; | ||
| private: | ||
| mutable std::string baseUrl; | ||
| bool verbose = false; |
There was a problem hiding this comment.
Is this a bad way to debug / set flags? I wasn't able to understand how to properly set debug flags within wasm (something like TF_DEBUG). Is that possible?
Description of Change(s)