You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So as to be less Azure Dependant and be more Web oriented, it would be nice if we could start browsing by just giving the URL of a SigMF Collection file. It would ease other people to share more of their IQ files.
I would like a new entry card on the home-page where I can provide the url of a SigMF collection that IQEngine could use to list IQ files available.
Care might be taken to handle access token to be forwarded on records retrieval
Describe alternatives you've considered
Other alternatives involved specific requests support for every different storage backend like very command S3. It would requires all plugin server support to every of those too.
The text was updated successfully, but these errors were encountered:
Interesting idea, so instead of providing a directory or storage account to find the list of recordings, you would provide the collection JSON which has the filenames of all the recordings within it. You would still have to provide the credentials needed to access all those recordings though.
It sounds like 1) you Collections support, which would be nice to have! and 2) you want the ability to use http/https file server instead of azure or the local server running the backend or opening a file local to the client, which are currently the only 3 options. I started looking into that, see #681 and maybe we can use that or a new Issue to talk about the idea of serving files with http. That way the Collections part can be discussed separately, since that's a different set of business logic and design.
So as to be less Azure Dependant and be more Web oriented, it would be nice if we could start browsing by just giving the URL of a SigMF Collection file. It would ease other people to share more of their IQ files.
I would like a new entry card on the home-page where I can provide the url of a SigMF collection that IQEngine could use to list IQ files available.
Care might be taken to handle access token to be forwarded on records retrieval
Describe alternatives you've considered
Other alternatives involved specific requests support for every different storage backend like very command S3. It would requires all plugin server support to every of those too.
The text was updated successfully, but these errors were encountered: