We need to add a field in the routes db to check if the given route has already been deployed.

[fdojurado]

This is needed to avoid sending duplicate routes.

Currently, we are saving the routes found using the routing algorithm in the historical-routes db, and we assume that previous routes in db have been already deployed.

However, this might not be always the case. We potentially need to use a flag to identify which routes have been deployed. This flag inherits the status from the historical routes.

One solution is to check if the routes already exist in the node. See issue #16

[fdojurado]

This is fixed in commit 8cc57cb

[fdojurado]

This is fixed in commit 8cc57cb

This has to be revised as the "save_routes_db" method doesn't look properly for matches in the "routes" field of the "nodes" collection.

[fdojurado]

One way to check if the routes already exist can be found in d7dcb05