[Boost.Asio] service_name/port inconsistency

Hi.

When designing server-client model, one has to use
boost::asio::ip::tcp::endpoint and boost::asio::ip::tcp::resolver::query
respectively. What I am confused about is that query accepts
std::string& service as a parameter whereas endpoint only accepts
unsigned short.

When writing code, it is really easy to get confused which constructor
takes string and which short. I would appreciate is somebody could
tell me if there is a way to create a server side component using
integer as a service.

- V