API suggestion

[jfirebaugh]

API suggestion

[DennisOSRM]

Is this for NodeJS or browser?

The shared memory stuff is backend only, ie. the browser shouldn't know about it

[jfirebaugh]

This is for the node-OSRM API.

[DennisOSRM]

Ok, cool. We shouldn't use any ini file as thats purely optional and deprecated now. The C++ way to do it now is to populate an unordered map with the paths and pass it to the OSRM c'tor:

https://github.com/DennisOSRM/Project-OSRM/blob/develop/Util/ServerPaths.h

So passing the filenames directly sounds better to me.

[jfirebaugh]

👍

[DennisOSRM]

A convenient feature would be just to give the base name, i.e '/path/to/file.osrm' and the 'new.Engine(...)' call adds the appropriate suffixes assuming that all files are in the same directory.

[jfirebaugh]

@DennisOSRM Seems like that should built into the C++ API and then just naturally be supported by the Node bindings.

[DennisOSRM]

@jfirebaugh Ok, is on the todo-list. If the user supplies an .osrm file instead of an .ini it will do it's magic automatically. For now, let's continue with an .ini file. This can then be added in due time. Does that make sense?

[springmeyer]

I'm starting to take a look at this.

[jfirebaugh]

Config part of this is done. Engine should still have dedicated route, locate, and nearest functions to replace Query.