{"push_id":678458748,"size":1,"distinct_size":1,"ref":"refs/heads/topic/direct-connections-revised","head":"be12e1536ba591ab0e63bd300b1e101a4e86acbe","before":"0a07f71625a19d4e3f6d7c69d4f661230b216f6d","commits":[{"sha":"be12e1536ba591ab0e63bd300b1e101a4e86acbe","author":{"email":"248ab303ce4621a021774f9b0c59b076bcd0c2b9@icir.org","name":"Matthias Vallentin"},"message":"Establish direct connections for indirect routes.\n\nThis change changes the behavior of the BASP broker when encountering\nindirect routes, i.e., routes for which no direct connections exist.\nIf the BASP broker now encounters an indrect route, it will attempt to\nestablish a direct connection to the remote node.\n\nFurther changes:\n\n  - When adding a new auxiliary/alternative route via add_route(), we\n    now insert the node ID for the corresponding next hop, as opposed to\n    the node ID of the final destination. This allows us to determine\n    whether a route is over a direct connection.\n\n  - The connection context now owns the client_handshake_data. It used\n    to have a non-owning pointer, but since the BASP broker itself now\n    also inserts a client handshake data and must not block at the same\n    time, the data needs to live in the broker itself. This change also\n    concerns io::remote_actor().\n\nINCOMPLETE COMMIT","distinct":true,"url":"https://api.github.com/repos/actor-framework/actor-framework/commits/be12e1536ba591ab0e63bd300b1e101a4e86acbe"}]}