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

What are the benefits of node-osrm over osrm-routed in production? #5331

Closed
RajibChanda opened this issue Jan 1, 2019 · 4 comments
Closed

Comments

@RajibChanda
Copy link

No description provided.

@systemed
Copy link
Member

systemed commented Jan 1, 2019

osrm-routed is not really a production HTTP server. It almost certainly has vulnerabilities and does not support anything like full HTTP functionality.

@danpat
Copy link
Member

danpat commented Jan 2, 2019

Some work has been done to replace osrm-routed C++ with a NodeJS/ExpressJS equivalent, but neither has been merged yet. It's on my "I want to get this finished one day" list:

Issue: #3832
Pull request: #4604

Note that the route.project-osrm.org demoserver is running the NodeJS version above, not the C++ osrm-routed server.

@quiqua
Copy link
Contributor

quiqua commented Jan 3, 2019

There is also this example https://github.com/door2door-io/osrm-express-server-demo, but still uses OSRM v5.16

@danpat
Copy link
Member

danpat commented Jan 28, 2019

Nothing actionable here - #3832 and #4604 track the NodeJS osrm-routed implementation.

@danpat danpat closed this as completed Jan 28, 2019
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

No branches or pull requests

4 participants