Boost Asio Io_Service vs Io_Context
I Am Using Boost Asio Library with C++. I Found That Io_Service and Io_Context Have Similarities. for Example Both Have Method Run and Others. Could Someone...
I am using boost asio library with c++. I found that io_service and io_context have similarities. for example both have method run and others. Could someone please detail differences between these two classes( like usage, conceptual idea, structural difference et.c)
1 Answer
You should use io_context, it replaces io_service.
According to boost issue #110:
io_serviceis deprecated. Yes, you should useio_context. Beware that the "old" API is deprecated as well (e.g.io_service.post(), you should usepost(io_context, handler)).. . .
io_service->io_context
io_service.post()->io_context.get_executor().post()
io_service.dispatch()->io_context.get_executor().dispatch()
io_service::strand->strand<io_context::executor_type>there were also changes to composed operation customization hooks - there are only 2 now -
boost::asio::associated_allocatorandboost::asio::associated_executor, which default to looking forget_allocator(), get_executor(),T::allocator_type,T::executor_typemembers of the composed operation function object.This is not a complete list.
These changes are related to Networking TS compatibility.
Seems to have been added in Boost 1.66.
Chloe Bennett explores the intersection of pop culture, streaming entertainment, digital trends, and contemporary lifestyle. Her weekly commentary reaches thousands of culture enthusiasts.
