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

[WIP] [SVCS-325] Proof of concept: Notify users after returning a 202 Accepted? #226

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

TomBaxter
Copy link
Member

@TomBaxter TomBaxter commented May 22, 2017

Task returns "Content-Location" header along with 202
Content-Location points to new /pending end-point
Upon task completion /pending end-point return 303 and "Content-Location" header
Pending Content-Location header returns uri of created/updated resource.

Requires redis. OSF PR 7255

[#SVCS-325]

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.2%) to 75.519% when pulling 1cead29 on TomBaxter:feature/svcs-325 into 425a329 on CenterForOpenScience:develop.

Task returns "Content-Location" header along with 202
Content-Location points to new /pending end-point
Upon task completion /pending end-point return 303 and "Content-Location" header
Pending Content-Location header returns uri of created/updated resource.
@coveralls
Copy link

coveralls commented Nov 14, 2017

Coverage Status

Coverage decreased (-0.2%) to 89.715% when pulling 21056ed on TomBaxter:feature/svcs-325 into 26bf209 on CenterForOpenScience:develop.

Copy link
Contributor

@cslzchen cslzchen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • Currently we inform the users of the success/failure by sending them an email upon finish/error. Does this solve the needs already? Or we want something more here? The original analysis ticket dated back to 2015 but the most recent one was just a year old. This makes me wonder whether there is still a need or not.

  • This PR and it's OSF counterpart seems unfinished. In addition, The page which provides some insight on the initial investigation for this PR seems unfinished as well. I am not able to get a general idea of the approach taken here and I don't know how Redis helps here. Need more discussion.

@cslzchen cslzchen self-assigned this Jun 27, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants