Option for building without Asio at all

[Cobaltergeist]

The program I'm hoping to integrate this with already has various utilities for work queues and network communications available, and I'm considering implementing my own overrides of delayed_task_scheduler, rpc_client_factory, rpc_listener, etc. as wrappers to those utilities. However, there's no way to completely remove the dependency on Asio, which would become dead weight in this case.

My project is storage-constrained, and I plan to consume Nuraft as a dynamic library so I can't rely on the linker dropping uncalled code. I already plan to use DISABLE_SSL to cut out one static dependency, and a means to cut out the other one would be very useful.

Thoughts on adding DISABLE_ASIO?

[greensky00]

At a glance, adding DISABLE_ASIO and removing Asio from the library don't seem difficult. But need to look further if there is any complicated build issue that requires code change. Actually raft_server_test is already running in that way with a mock network/timer layer, it is still compiled with Asio though. Will update in this thread shortly.

[greensky00]

Now you can refer to https://github.com/eBay/NuRaft/blob/master/docs/customizing_asio.md#integrating-your-own-implementation