Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Need to set a Custom Timout of Consumption of Datasets #306

Closed
kaimeinke opened this issue Dec 29, 2020 · 3 comments
Closed

Need to set a Custom Timout of Consumption of Datasets #306

kaimeinke opened this issue Dec 29, 2020 · 3 comments

Comments

@kaimeinke
Copy link

Dear Developers,

we need to configure the consumption timeout of a dataset to restrict unlimited downloads of the set.

Currently the timeout default is 0 [infinite].

We want to change this to somewhere between 3600 [1h] or 86400 [24h] so enable a confortable download, but at the same time restrict the opportunity of infinite downloads, since the underlying data is subject to change and shall be bought multiple times.

Could this value be integrated in the "Publish GUI" and in the "Edit Metadata" GUI or could you give us a way to change this for a specific asset through a beta/dev function we could use?

{
"type": "access",
"index": 1,
"serviceEndpoint": "https://provider.mainnet.oceanprotocol.com",
"attributes": {
"main": {
"creator": ".........",
"datePublished": "...........",
"cost": "1",
"timeout": 0,
"name": "dataAssetAccess"
}
}
}

@kaimeinke
Copy link
Author

Maybe this is already been taken care of in the publish form in #272 if I get it right? Would this work for the edit function as well? This would solve our problem.

@alexcos20 alexcos20 linked a pull request Jan 8, 2021 that will close this issue
@kaimeinke
Copy link
Author

After talking to @alexcos20 , this issue would be the one to solve the edit timeout problem. #310

@kremalicious
Copy link
Contributor

closing in favor of #202

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants