checkURL interface

[alexcos20]

No description provided.

[calina-c]

nice :D

[kremalicious]

So is it possible to get that method without initializing the whole ocean object? Otherwise we would need to block adding any files in UI as long as user does not have any wallet connected

[kremalicious]

not sure yet why oceanprotocol/provider#57 introduces /checkUrl & /assetInfo and what is best to use here

[alexcos20]

So is it possible to get that method without initializing the whole ocean object? Otherwise we would need to block adding any files in UI as long as user does not have any wallet connected

You need a provider class. That should be possible without web3

[alexcos20]

not sure yet why oceanprotocol/provider#57 introduces /checkUrl & /assetInfo and what is best to use here

checkUrl takes an URL (http:///www.example.com) and check if your selected provider is able to access it and gets file information (length & type)
/assetInfo takes a DID with some files (you don't have the URLs) and will send back the same interface, but with updated values.

Let's say that you published www.example.com as DID1. and you are updating the content, but in the DDO you still have the old length of the file. By calling /assetInfo, provider can decrypt the URLs , check if they are still valid, get the file info and then you can update your DDO with the new info

[codeclimate]

Code Climate has analyzed commit 2a1af0d and detected 0 issues on this pull request.

The test coverage on the diff in this pull request is 83.3% (50% is the threshold).

This pull request will bring the total coverage in the repository to 77.7% (0.2% change).

View more on Code Climate.

[alexcos20]

superseded by #544