From Wikipedia, the free encyclopedia
This article needs additional citations for . Please help
by . Unsourced material may be challenged and removed. (July 2010) ()
In , the Windows Sockets API (WSA), later shortened to Winsock, is a technical specification that defines how
should access , especially . It defines a standard interface between a Windows
client application (such as an
or a ) and the underlying TCP/IP . The nomenclature is based on the
model used in
for communications between programs.
Early Microsoft operating systems, both MS-DOS and Microsoft Windows, offered limited networking capability, chiefly based on . In particular, Microsoft did not offer support for the TCP/IP protocol stack at that time. A number of university groups and commercial vendors, including the PC/IP group at , FTP Software, , , and , introduced TCP/IP products for MS-DOS, often as part of a hardware/software bundle. When
was released, these vendors were joined by others such as Distinct and
in offering TCP/IP for Windows.
The drawback faced by all of these vendors was that each of them used their own API (Application Programming Interface). Without a single standard programming model, it was difficult to persuade independent software developers to create networking applications which would work with any vendor’s underlying TCP/IP implementation. Add to this the fact that end users were wary of getting locked into a single vendor and it became clear that some standardization was needed.
The Windows Sockets API was proposed by Martin Hall of JSB Software (later Stardust Technologies) in a "BoF" () discussion on the
network in October 1991.[] The first edition of the specification was authored by Martin Hall, Mark Towfiq of Microdyne (later ), Geoff Arnold of , and Henry Sanders and
of , with assistance from many others.[] There was some discussion about how best to address the copyright, intellectual property, and potential anti-trust issues, and consideration was given to working through the
or establishing a non-profit foundation. In the end, it was decided that the specification would simply be copyrighted by the five authors as (unaffiliated) individuals.
All the participating developers resisted the shortening of the name to simple Winsock for a long time,[] since there was much confusion among users between the API and the DLL library file (winsock.dll) which only exposed the common WSA interfaces to applications above it. Users would commonly believe that only making sure the
file was present on a system would provide full TCP/IP protocol support.[]
The Windows Sockets API specification defines two interfaces: the
developers, and the , which provides a means for network software developers to add new protocol modules to the system. Each interface represents a contract. The
guarantees that a conforming application will function correctly with a conforming protocol implementation from any network software vendor. The
contract guarantees that a conforming protocol module may be added to Windows and will thereby be usable by an API-compliant application. Although these contracts were important when Windows Sockets was first released, since network environments required multi-protocol support (see above) they are now of only academic interest. Included in the Windows Sockets API version 2.0 are functions to use , although the protocol was all but obsolete already at the time WSA 2.0 shipped.
has shipped the
protocol stack with all recent versions of Windows, and there are no significant independent alternatives. Nor has there been significant interest in implementing protocols other than TCP/IP.
Windows Sockets code and design are based on , but provides additional functionality to allow the API to comply with the regular Windows programming model. The Windows Sockets API covered almost all the features of the
API, but there were some unavoidable obstacles which mostly arose out of fundamental differences between Windows and
(though Windows Sockets differed less from
than the latter did from ). All function calls in the
begin with the
WSA, e.g. WSASend() for sending data on a connected socket.
However it was a design goal of Windows Sockets that it should be relatively easy for developers to port socket-based applications from
to Windows. It was not considered sufficient to create an API which was only useful for newly written Windows programs. For this reason, Windows Sockets included a number of elements which were designed to facilitate porting. For example,
applications were able to use the same
to record both networking errors and errors detected within
functions. Since this was not possible in Windows, Windows Sockets introduced a dedicated function, WSAGetLastError(), to retrieve error information. Such mechanisms were helpful, but application porting remained extremely complex. Many original
applications had been implemented by using system features specific to , such as
and the , and reproducing such functionality in Windows was problematic. Within a relatively short time, porting gave way to the development of dedicated Windows applications.
Version 1.0 (June 1992) defined the basic operation of Winsock. It was kept very close to the existing interface of Berkeley sockets to simplify porting of existing applications. A few Windows-specific extensions were added, mainly for asynchronous operations with message-based notifications.
Although the document didn't limit support to TCP/IP, TCP and UDP were the only protocols explicitly mentioned. Most vendors only delivered TCP/IP support, although Winsock from
support as well.
Version 1.1 (January 1993) made many minor corrections and clarifications of the specification. The most significant change was the inclusion of the gethostname() function.
Winsock 2 was a
extension of Winsock 1.1. It added support for protocol-independent name resolution, asynchronous operations with event-based notifications and completion routines, layered protocol implementations, , and . It also formalized support for multiple protocols, including
and . The new specification allowed sockets to be optionally shared between processes, incoming connection requests to be conditionally accepted, and certain operations to be performed on socket groups rather than individual sockets. Although the new specification differed substantially from Winsock 1, it provided source- and binary-level compatibility with the Winsock 1.1 API. One of the lesser known additions was the Service Provider Interface (SPI) API and .
Versions 2.0.x (May 1994 onwards) had internal draft status, and were not announced as public standards.
Version 2.1.0 (January 1996) was the first public release of the Winsock 2 specification.
Version 2.2.0 (May 1996) included many minor corrections, clarifications, and usage recommendations. It was also the first version to remove support for 16-bit Windows applications.
Version 2.2.1 (May 1997) and Version 2.2.2 (August 1997) introduced minor functionality enhancements. Mechanisms were added for querying and receiving notification of changes in network and system configuration.
Technical Preview for
(December 2000) saw the first implementation of
(March 1999, later obsoleted by ), a protocol-independent API for name resolution, which would become part of Winsock in .
includes the "RIO" (Registered IO) extensions for Winsock. These extensions are designed to reduce the overhead of the user to kernel mode transition for the network data path and the notification path, but use the rest of the regular Windows TCP and UDP stack (and uses existing network cards). The setup path (for example, the "connect" function) is unchanged from the regular Winsock path.
Microsoft did not supply an implementation of Winsock 1.0.
Version 1.1 of Winsock was supplied in an add-on package (called Wolverine) for Windows for Workgroups (code named Snowball). It was an integral component of Windows 95 and
from versions 3.5 and onwards (the initial commercially available version of Windows NT, version 3.1, included only a proprietary and quite incomplete implementation of TCP/IP based on the AT&T UNIX System V "STREAMS" API[]).
Version 2.1 of Winsock was supplied in an add-on package for Windows 95. It was an integral component of , , and all subsequent Windows releases. (Microsoft did not supply implementations of Winsock 2 for Windows 3.x or Windows NT 3.x.)
Recent versions of Winsock 2.x have been delivered with new Windows releases or as part of service packs.
Winsock 2 is extensible by a mechanism known as a
(LSP). Winsock LSPs are available for a wide range of useful purposes, including Internet parental controls, web content filtering,
etc. The layering order of all providers is kept in the Winsock Catalog. In previous versions of Windows, removing a buggy LSP could result in corruption of the Winsock catalog in the registry, potentially resulting in a loss of all network connectivity. Winsock in Windows XP Service Pack 2, Windows Server 2003 Service Pack 1 and all later Windows operating systems has the ability to self-heal after a user uninstalls such an LSP.
Among the other vendors offering Winsock-compliant TCP/IP and UDP/IP stacks were (alphabetically) , Beame & Whiteside, DEC, Distinct, , Frontier, , Microdyne, , ,
and Trumpet Software International.
Trumpet Winsock was one of the few Winsock 1.0 implementations that could be installed under , which had no built-in support for Winsock. Trumpet was also the most popular
implementation of Winsock for Windows 3.x. Trumpet Winsock 5.0 is available for / and
and includes a Winsock 1.1 compliant IPv6 stack for these operating systems.
(Winsock LSP)
- Windows Sockets FAQ
- Winsock C++ Programming
— Microsoft developer blog covering Winsock, WSK, WinINet, Http.sys, WinHttp, QoS and System.Net, with a focus on features being introduced in
with descriptions
: Hidden categories:发现一只腾讯养的狗，【tgp吧】_百度贴吧
&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&签到排名：今日本吧第个签到，本吧因你更精彩，明天继续来努力！
本吧签到人数：0成为超级会员，使用一键签到本月漏签0次！成为超级会员，赠送8张补签卡连续签到：天&&累计签到：天超级会员单次开通12个月以上，赠送连续签到卡3张
关注：16,809贴子：
发现一只腾讯养的狗，收藏
鳄鱼的眼泪238
奇迹重生，重铸辉煌，新版魔剑士归来！海量钻石，众多好礼，你敢拿我就送！
登录百度帐号推荐应用后使用快捷导航没有帐号？
查看: 2974|回复: 31
沒個性丶不簽名
新人欢迎积分1 阅读权限105积分114987精华0UID帖子金钱1775 威望10
能用手解决的事情,就不要去糟蹋一个姑娘
Lv.12, 积分 114987, 距离下一级还需 20013 积分
UID帖子威望10 多玩草339 草
我发个战绩图片是tgp图它就不愿意了，那你玩腾讯游戏来多玩是什么狗？
(48.88 KB, 下载次数: 2)
10:54:40 上传
下载次数: 2
&不要喷全部
新人欢迎积分1 阅读权限60积分3753精华0UID帖子金钱11593 威望0
Lv.6, 积分 3753, 距离下一级还需 1247 积分
UID帖子威望0 多玩草30 草
寒冰大大为人人&&别以为你换了马甲 我就不知道是你& && &&&
新人欢迎积分1 阅读权限80积分12853精华0UID帖子金钱5039 威望2
Lv.8, 积分 12853, 距离下一级还需 7147 积分
UID帖子威望2 多玩草782 草
自找没趣...自己被喷还要乱放AOE...
新人欢迎积分1 阅读权限40积分926精华0UID帖子金钱9727 威望0
Lv.4, 积分 926, 距离下一级还需 74 积分
UID帖子威望0 多玩草0 草
T!G!P!狗！
新人欢迎积分1 阅读权限99积分46264精华0UID帖子金钱111695 威望11
Lv.10, 积分 46264, 距离下一级还需 8736 积分
UID帖子威望11 多玩草1103 草
最近游戏，什么插件都没习惯开，果奔，
新人欢迎积分1 阅读权限60积分4229精华0UID帖子金钱24466 威望0
Lv.6, 积分 4229, 距离下一级还需 771 积分
UID帖子威望0 多玩草1034 草
自找没趣，我只是随便说说
新人欢迎积分1 阅读权限40积分865精华0UID帖子金钱8938 威望0
Lv.4, 积分 865, 距离下一级还需 135 积分
UID帖子威望0 多玩草0 草
T G P&&GOU& &
新人欢迎积分1 阅读权限80积分14257精华0UID帖子金钱347518 威望1
Lv.8, 积分 14257, 距离下一级还需 5743 积分
UID帖子威望1 多玩草368 草
论坛什么人都有的
新人欢迎积分1 阅读权限80积分10459精华0UID帖子金钱35217 威望2
Lv.8, 积分 10459, 距离下一级还需 9541 积分
UID帖子威望2 多玩草1332 草
表示现在盒子能吸引大家的不就是个论坛吗& &我一样用的TGP
&主要还是开加速还有不输密码&
看什么看我就是不填资料 而你无可奈何
新人欢迎积分0 阅读权限60积分3456精华0UID帖子金钱15452 威望0
Lv.6, 积分 3456, 距离下一级还需 1544 积分
UID帖子威望0 多玩草30 草
TGP& && &&&GOU ,我是用盒子的
新人欢迎积分1 阅读权限40积分563精华0UID帖子金钱1660 威望0
Lv.4, 积分 563, 距离下一级还需 437 积分
UID帖子威望0 多玩草0 草
TGP& & GOU& && && &&&
中毒极深的孩纸
新人欢迎积分1 阅读权限70积分7218精华0UID帖子金钱4241 威望0
Lv.7, 积分 7218, 距离下一级还需 2782 积分
UID帖子威望0 多玩草87 草
那人骂的有点过了....用TGP难道是被骂的理由吗，虽然我用TGP都是看战绩的
新人欢迎积分0 阅读权限10积分10精华0UID帖子金钱79 威望0
Lv.1, 积分 10, 距离下一级还需 5 积分
UID帖子威望0 多玩草0 草
人分三等& &一种是有东西会用得
一种是有东西不会用的
还有一种是有东西不用还特么不准别人用得。
新人欢迎积分1 阅读权限70积分7715精华0UID帖子金钱114794 威望2
丧心病狂的尤尤
Lv.7, 积分 7715, 距离下一级还需 2285 积分
UID帖子威望2 多玩草20 草
从此我的词库又多了一个
新人欢迎积分0 阅读权限30积分112精华0UID帖子金钱3010 威望0
Lv.3, 积分 112, 距离下一级还需 138 积分
UID帖子威望0 多玩草0 草
tgp助手并不喜欢，虽然感觉方便点，但是用盒子是一种信仰
初级灌水标兵
初级灌水标兵
爱情守望者
爱情守望者
初级在线标兵
论坛在线时间达1000小时即可申请
风雨同舟勋章
一路有你，多玩更精彩
365天！天天有你
连续签到1年即可获得
猴年新春勋章
猴年大吉，猴年行大运！
英雄联盟赛事勋章
英雄联盟赛事勋章
LOL战斗力9000以上
手机论坛勋章
APP发帖双倍积分，登陆即送勋章！
一路有你，感恩相伴
活动奖励勋章
活动奖励勋章
话题王小红花
话题王小红花
节日守望者
节日守望者
LOL手机盒子勋章
据说下载了LOL手机盒子APP才能拥有
时尚爆米花勋章
需要金钱：1100
手机盒子客户端点击或扫描下载
Powered bywin8系统出现ierd_tgp_lsp.dll没有被指定_百度知道
色情、暴力
我们会通过消息、邮箱等方式尽快将举报结果通知您。
win8系统出现ierd_tgp_lsp.dll没有被指定
如图这个问题要怎么解决啊！求大神帮忙
我有更好的答案
运行cmdDOS界面：输入：CD\然后：netsh winsock reset搞定。我跟你一样，弄好了
按回车键。然后输入，输入:CD&#92，右键以管理员的身份运行，说一下吧:window8的左键菜单，找到命令提示符，点击↓这个符号我的也刚弄好
删除NVidia驱动然后重新安装。
为您推荐：
其他类似问题
妇科医院的相关知识
换一换
回答问题，赢新手礼包