#include <cstdlib>
#include <iostream>
#include <boost/bind.hpp>
#include <boost/asio.hpp>
using boost::asio::ip::tcp;
class session
{
public:
session(boost::asio::io_service& io_service)
: socket_(io_service)
{
}
tcp::socket& socket()
{
return socket_;
}
void start()
{
socket_.async_read_some(boost::asio::buffer(data_, max_length - 1),
boost::bind(&session::handle_read, this,
boost::asio::placeholders::error,
boost::asio::placeholders::bytes_transferred));
}
void handle_read(const boost::system::error_code& error,
size_t bytes_transferred)
{
if (!error)
{
data_[bytes_transferred] = '\0';
if(NULL != strstr(data_, "quit"))
{
this->socket().shutdown(boost::asio::ip::tcp::socket::shutdown_both);
this->socket().close(); // how to make this dispatch "handle_read()" with a "disconnected" flag?
}
else
{
boost::asio::async_write(socket_,
boost::asio::buffer(data_, bytes_transferred),
boost::bind(&session::handle_write, this,
boost::asio::placeholders::error));
socket_.async_read_some(boost::asio::buffer(data_, max_length - 1),
boost::bind(&session::handle_read, this,
boost::asio::placeholders::error,
boost::asio::placeholders::bytes_transferred));
}
}
else
{
delete this;
}
}
void handle_write(const boost::system::error_code& error)
{
if (!error)
{
//
}
else
{
delete this;
}
}
private:
tcp::socket socket_;
enum { max_length = 1024 };
char data_[max_length];
};
class server
{
public:
server(boost::asio::io_service& io_service, short port)
: io_service_(io_service),
acceptor_(io_service, tcp::endpoint(tcp::v4(), port))
{
session* new_session = new session(io_service_);
acceptor_.async_accept(new_session->socket(),
boost::bind(&server::handle_accept, this, new_session,
boost::asio::placeholders::error));
}
void handle_accept(session* new_session,
const boost::system::error_code& error)
{
if (!error)
{
new_session->start();
new_session = new session(io_service_);
acceptor_.async_accept(new_session->socket(),
boost::bind(&server::handle_accept, this, new_session,
boost::asio::placeholders::error));
}
else
{
delete new_session;
}
}
private:
boost::asio::io_service& io_service_;
tcp::acceptor acceptor_;
};
int main(int argc, char* argv[])
{
try
{
if (argc != 2)
{
std::cerr << "Usage: async_tcp_echo_server <port>\n";
return 1;
}
boost::asio::io_service io_service;
using namespace std; // For atoi.
server s(io_service, atoi(argv[1]));
io_service.run();
}
catch (std::exception& e)
{
std::cerr << "Exception: " << e.what() << "\n";
}
return 0;
}
While experimenting with boost::asio I’ve noticed that within the calls to async_write()/async_read_some() there is a usage of the C++ “new” keyword.
Also, when stressing this echo server with a client (1 connection) that sends for example 100,000 times some data, the memory usage of this program is getting higher and higher.
What’s going on? Will it allocate memory for every call? Or am I wrong? Asking because it doesn’t seem right that a server app will allocate, anything. Can I handle it, say with a memory pool?
Another side-question:
See the “this->socket().close();” ?
I want it, as the comment right to it says, to dispatch that same function one last time, with a disconnection error. Need that to do some clean-up. How do I do that?
Thank you all gurus (:
In the hope that someone will contribute something…
Further in my experiments at boost::asio I’ve decided that right after the server app is up & running I’ll put a breakpoint at C++’s ‘new’ code, i.e at “new.cpp” @ function “void *__CRTDECL operator new(size_t size) _THROW1(_STD bad_alloc)”. Note, I’m using MSVC 2008.
Using the code above, of the original post:
Now that the BP is on I’m connecting one client.
Allocation is done (several times) (as expected) (I know it because the debugger stops at the ‘new’ keyword as I set) and the new client is now ready to send/receive data.
I send “hi” from the client to the server.
The BP at ‘new’ is hit at handle_read().
The source to is was the call to async_write() (I stack trace with MSVC).
Hitting F5 (continue) generates another breakpoint at ‘new’ – this time the async_read_some() call generated it.
Conclusion:
Each such operation generates a call to ‘new’ !!!!!! Worst case a real server might have!
So, further on looking for some way to use some sort of memory pool so these ‘new’ calls won’t exist brought me to the example: “allocation”.
Path to it: “…….\boost_1_43_0\libs\asio\example\allocation\”.
Doing the same with this new code (written below) gave me cheering results;
Calls to async_write() and async_read_some() do not generate a call to ‘new’.
So far it’s nice, but to be honest I can’t say I understand exactly how this is done; The allocator is broke down into several pieces as you can see, and that makes things a bit confusing to me.
make_custom_alloc_handler() <— what exactly does it do?
What’s shared_from_this()??
I see that a “session” object has the member “handler_allocator allocator_”. Does every “session” object holds a pool of these objects?! Can I have one of this, at the “server” class level which will be shared or something?
“allocator” example code: