国产精品剧情在线亚洲,日韩系列欧美系列,亚洲人成艺术

acceptor两种创徏�Ҏ��

Enic — Thu, 16 Mar 2017 13:56:00 GMT

1.创徏的时候给明确地址和端口，创徏完成后直接可以accept
2.open bind listen accept完整套�\

Enic 2017-03-16 21:56 发表评论

Enic — Thu, 16 Mar 2017 13:54:00 GMT

1.直接close�Q�客��L��接收数据不完��_��本地�pȝ��关闭socket�Q�客��L��收不到完整数�?/div>

2.shutdown_both�Q�客��L��接收数据不完��_��end of file

3.shutdown_receive: 客户端接收数据完�?/div>

3.shutdown_send: 客户端接收数据不完整,�q�程��L��关闭链接

关闭socket�Q�但是确保对端一定收到数据的手段是：

1.shutdown_receive,同时在应用层��认全部数据已经投递到tcp堆栈�Q�然后调用close

2.设计应用层关闭协议，由接收方��d��关闭

Enic 2017-03-16 21:54 发表评论

asio.hpp和windows.h冲突解决

Enic — Fri, 14 Feb 2014 03:53:00 GMT

开始��用boost::asio库时�Q�编译碰到这个错误提�C�：

fatal error C1189: #error : WinSock.h has already been included

查了下抛��个错误的boost代码�Q�原来是定义了_WINSOCKAPI_�Q�但没有定义_WINSOCK2API_

那哪里定义了_WINSOCKAPI_呢？

后来在网上查了下�Q�原来是我包含了Windows.h头文�Ӟ��而Windows.h头文件又包含了WinSock.h�q�个老东�?/p>

知道原因��q��单了�Q�试了下�Q�方法有三种可解��x��错误�Q?/p>

1、在包含Windows.h前定义宏WIN32_LEAN_AND_MEAN�Q�就OK了（WIN32_LEAN_AND_MEAN表示不包含一些极��用和偏门的资料）

2、在包含Windows.h前包含winsock2.h

3、在包含Windows.h前包含asio.hpp

Enic 2014-02-14 11:53 发表评论

Enic — Fri, 08 Mar 2013 10:04:00 GMT

// learn_boost_asio.cpp : 定义控制台应用程序的入口炏V�?/div>

#include "stdafx.h"

#include

namespace asio = boost::asio;

namespace posix_time = boost::posix_time ;

// 1.同步定时器��?/div>

void LeanrHowToUseSynchronouslyTimer()

{

asio::io_service io;

asio::deadline_timer deadLineTimer(io, posix_time::seconds(3));

boost::timer timerTestDeadLineTimer;

timerTestDeadLineTimer.restart();

deadLineTimer.wait();

double dTime = timerTestDeadLineTimer.elapsed();

std::cout << dTime << std::endl;

}

////////~

// 2.异步定时器��?/div>

class CSomeObject

{

public:

CSomeObject(asio::io_service& ioService) :

m_deadLineTimer(ioService)

{

}

public:

void Test()

{

m_deadLineTimer.expires_from_now(boost::posix_time::seconds(3));

m_timerTestDeadTimer.restart();

m_deadLineTimer.async_wait(

boost::bind(&CSomeObject::TimerHandler, this, asio::placeholders::error));

}

public:

void TimerHandler(const boost::system::error_code&)

{

double dTime = m_timerTestDeadTimer.elapsed();

std::cout << "time passed: " << dTime << std::endl;

}

private:

boost::timer m_timerTestDeadTimer;

asio::deadline_timer m_deadLineTimer;

};

void LearnHowToUseAsynchronouslyTimer()

{

asio::io_service ioService;

CSomeObject obj(ioService);

obj.Test();

asio::io_service::work* pWork = new asio::io_service::work(ioService);

std::auto_ptr spWork(pWork);

ioService.run();

//spWork.reset(); // Allow run() to exit.

}

//////////////////////////////////////////

int _tmain(int argc, _TCHAR* argv[])

{

LearnHowToUseAsynchronouslyTimer();

return 0;

}

Enic 2013-03-08 18:04 发表评论

4.boost::asio 的handle理解

Enic — Thu, 08 Nov 2012 11:48:00 GMT

在asio的异步指导思想下，所有的socket io操作都被分解了：

投递请�?�?gt; 响应�l�果

投递请求是异步IO的发起动作，响应�l�果是异步IO的结果反馈动作�?/p>

具体��C��码就是：async�p�d��函数和Functor构成的handler

每一个操作对应一�U�handler

具体handler来说主要有两�U�模型：

一�U�是接收一个error和translateLen�Q�这可个详情可以看文档�?/p>

主要能理解async和handler�Q�和选择正确的handler

应该来说�Q�原则上所有有数据传输的handler有应该选择能接收len的Functor�Q�这��h��制能力更加精��?/p>

其他的细节有待分析，�Q�，

Enic 2012-11-08 19:48 发表评论

Enic — Wed, 07 Nov 2012 05:52:00 GMT

直白点说�Q�就是对getaddrinfo()�q�个函数的适配。抽象点说就是解析器�?

�l�节如下�Q?/p>

boost::asio::ip::tcp::resolver resolver(asioService);
boost::asio::ip::tcp::resolver::query queryEndpoints(boost::asio::ip::host_name(),"80");
boost::asio::ip::tcp::resolver::iterator endpoint_iterator = resolver.resolve(queryEndpoints);
;
for(boost::asio::ip::tcp::resolver::iterator iterNull;
    endpoint_iterator != iterNull;
    endpoint_iterator++)
{
    std::cout << endpoint_iterator->endpoint() << std::endl;
}

上面的代码有�q�么几个�c�d��Q?/p>

boost::asio::ip::tcp::resolver

boost::asio::ip::tcp::resolver::query

boost::asio::ip::tcp::resolver::iterator

resolver抽线的是getaddrinfo()动作

boost::asio::ip::tcp::resolver::query抽象的是getaddrinfo()需要的参数

boost::asio::ip::tcp::resolver::iterator抽象的是getaddrinfo()的结�?

�q�整个体�p�L��抽象winsock sdk到stl思想

Enic 2012-11-07 13:52 发表评论

Enic — Wed, 07 Nov 2012 02:27:00 GMT

原则上将会在处理完所有的异步��h��以后�q�回�Q�具体内部是某个变量控制的�?/p>

可以通过�Q?/p>

boost::asio::io_service io_service;

boost::asio::io_service::work work(io_service);

work构造以后会让io_service内部的某个控制变量自增这样run��׃��会返回了�?/p>

可以通过�c�M��q�样的技巧更漂亮的控�Ӟ��

boost::asio::io_service asioService;
//boost::asio::io_service::work work(asioService);
boost::scoped_ptr spWork(new boost::asio::io_service::work(asioService));
asioService.run(); // �q�样run��׃��一直执行不会返�?br />
...
spWork.reset();// reset会导致内部的work析构�Q�析构以后io_service里边的控刉��׃��正常。run处理完所有异步请求就会返回了

Enic 2012-11-07 10:27 发表评论

1.endpoint 一个socket体系中的�l�端标识

Enic — Tue, 06 Nov 2012 02:46:00 GMT

endpoint:描述socket�~�程体系下的一个端炏V��一个IP+PORT ?

port�q�是一��L��unsigned short

提供一个data()�Ҏ��Q�来�q�回原生的地址�l�构体。这是一个好的思�\�Q�这��L��l�就不会��闭了�?

address: 抽象的一个IP地址�Q�可以是ipv4、ipv6。对外接口一致。具体实��C��Q�是聚合�?�?两个实体。所以提供is_v4 is_v6�q�样两个函数来确认类型�?br> address只提供string到address的�{换和构造。具体到address_v6 address_v4以后有提供long到address_v4的�{换同时也提供了一�p�d��的帮助函敎ͼ�
/// Determine whether the address is a loopback address.
BOOST_ASIO_DECL bool is_loopback() const;

/// Determine whether the address is unspecified.
BOOST_ASIO_DECL bool is_unspecified() const;

/// Determine whether the address is a class A address.
BOOST_ASIO_DECL bool is_class_a() const;

/// Determine whether the address is a class B address.
BOOST_ASIO_DECL bool is_class_b() const;

/// Determine whether the address is a class C address.
BOOST_ASIO_DECL bool is_class_c() const;

/// Determine whether the address is a multicast address.
BOOST_ASIO_DECL bool is_multicast() const;
/// Obtain an address object that represents the loopback address.
static address_v4 loopback()
/// Obtain an address object that represents the broadcast address.
static address_v4 broadcast()

Enic 2012-11-06 10:46 发表评论