BRouter - Beta Version 0.9.4 - Using the service interface
==========================================================

Starting with version 0.9.3, BRouter contains a *NEW* service interface.

The HTTP-Interface introduced in 0.9.1-0.9.2 was dropped

The new service interface is an Android service that can be called
from other apps. See the file IBRouterService.aidl for the
interface definition.

OruxMaps starting with version 5.5.3 implements this interface.

The service interface defines a default timeout of 60 seconds
(if not modified by the caller), so you can only calculate
medium distance routes via the service interface. For long
distance calculations, you would run into the timeout, so
you have to use BRouter's classical operation mode
to do long-distance calculations.

The configuration concept in the service interface
--------------------------------------------------

BRouter is fully configurable via the use of profile
definition files and a list of nogo-areas, while
the service interface is usually accessed by just
choosing one o the 6 "standard routing modes" made
of a combination of the car/bike/foot and the
shortest/fastest selection.

Therefore, you need a mapping between the standard routing mode
and BRouter's configuration. There is no default mapping
deployed with the BRouter distribution file, so you have
to configure this yourself. You can do that by starting
BRouter is the "normal" way and at the end of the routing
process, press the "Server Mode" button. Then you get
a list of standard routing mode with a preselection,
where you can choose for which of the 6 standard modes
you want to store the configuration just used.
(profile + nogo-list). Please note that the profile
is stored by reference (so modifications at the profile
file afterwards will have effect), while the nogo-areas
are stored by value (so modifying the nogo-waypoints
afterwards will have no effect)
