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

NodeJs based Http Server #3887

Closed
wants to merge 1 commit into from
Closed

NodeJs based Http Server #3887

wants to merge 1 commit into from

Conversation

daniel-j-h
Copy link
Member

Resolves #3832.

Tasklist

  • Url parses, grammars
  • Hook up node-osrm bindings
  • Switch Cucumber tests to using this
  • update relevant Wiki pages
  • Battle test this
  • review
  • adjust for comments

@daniel-j-h
Copy link
Member Author

Stale. This is not specced out and feedback wrt. consolidating our internal server never happened.

@daniel-j-h daniel-j-h closed this May 15, 2017
@daniel-j-h daniel-j-h deleted the nodejs-server branch May 15, 2017 10:53
@emiltin
Copy link
Contributor

emiltin commented May 15, 2017

hmm. still sounds like a good idea, if the recommended way to run osm in production is node, not osrm-routed?

@daniel-j-h
Copy link
Member Author

Yes and that's why the issue is still open. I just closed this pull request since nothing was moving on that front and I don't want to keep it around in that state.

Switching osrm-routed to a Node.js based server and away from the crufty C++ HTTP server is still on the todo list just not a priority for us atm since we already do have a functioning HTTP server on top of node-osrm. Would require more coordination with our internal API (cc @freenerd @miccolis).

@emiltin
Copy link
Contributor

emiltin commented May 15, 2017

i see, makes sense

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

Successfully merging this pull request may close these issues.

2 participants