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

Optimize stub RDO calls #160

Open
Arithmomaniac opened this issue Dec 7, 2018 · 2 comments
Open

Optimize stub RDO calls #160

Arithmomaniac opened this issue Dec 7, 2018 · 2 comments

Comments

@Arithmomaniac
Copy link
Collaborator

There are use cases where a model might just need to contain an ArtifactID - for example, if you only care about the ArtifactID of an associative object.
A provider should skip work on these items for Get or Update operations, except to process any child objects (if they exist).

@mrobustelli
Copy link
Contributor

would need to check if only ArtifactID is populated before updates or any action.

@mrobustelli
Copy link
Contributor

@hhristov-tsd will work meet with his team 4/15. He will follow up with @mrobustelli after and we will decide path forward from there. We need an architectural vision before we start work.

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

No branches or pull requests

2 participants