Thanks, that’s great news!
The main reason we’re writing our own server is performance - we send quite a
bit of extra information with the request, so we’re using protocol buffers to
send compressed binaries between different languages.
Additionally, we don’t need any of the front end web stuff, as we’ve got our
own API and front end on top of the routing. Using a minimal socket based
solution, I've been able to implement the core functionality we need in around
100 lines of code.
Thanks,
Alex
On Thu, Jul 16, 2015 at 6:03 PM, Peter <[email protected]> wrote:
> Hi Alex,
> as long as you use the in-memory setting you are safe for multiple
> concurrent routing requests.
> But why implementing the server side handling from scratch as we offer
> this already via the web module?
> Kind Regards,
> Peter
> On 16.07.2015 18:53, Piemapping wrote:
>> Hi,
>>
>> I’m currently writing a simple socket server that uses GraphHopper to
>> respond to routing requests.
>>
>> Listening for clients is blocks, so I’m planning on having the main
>> thread block and spawn new threads to handle the routing request.
>>
>> Will it be possible to have multiple concurrent routing requests on
>> the same in-memory graph? If not, how much of a challenge would
>> implementing this be?
>>
>> Thanks,
>> Alex
> _______________________________________________
> GraphHopper mailing list
> [email protected]
> https://lists.openstreetmap.org/listinfo/graphhopper
_______________________________________________
GraphHopper mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/graphhopper
