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

Make a truly async model pipeline work for WebApi publisher. #322

Closed
wants to merge 1 commit into from
Closed

Make a truly async model pipeline work for WebApi publisher. #322

wants to merge 1 commit into from

Conversation

rayao
Copy link
Contributor

@rayao rayao commented Mar 14, 2016

A truly async model pipeline leads to unsuccessful routing registration. We didn't see this in our existing samples because their model pipelines are synchronous in nature.
This change tries to defer the actual RESTier routing setup until the model pipeline returns. Before that, requests run on a placeholder routing.

@rayao
Copy link
Contributor Author

rayao commented Mar 14, 2016

#304

batchHandler.ApiFactory = apiFactory;
}
var pathHandler = new DefaultODataPathHandler();
////defaultODataPathHandler.ResolverSetttings = config.GetResolverSettings();
Copy link
Contributor Author

Choose a reason for hiding this comment

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

ResolverSettings is an internal member, must find a way to set it if no other convenient API.

@rayao
Copy link
Contributor Author

rayao commented Mar 14, 2016

I'm not quite sure if we should go this way. Another option is to force the model pipeline synchronous.

@lewischeng-ms
Copy link
Contributor

@rayao, based on our offline discussion, please change the PR accordingly and merge. Thanks!

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 this pull request may close these issues.

None yet

4 participants