然后，我在WSDL实现中收集服务和端口，该实现为这个绑定提供一个端点。
Then I glean the service and port in the WSDL implementation that provides an endpoint for this binding.
不过，的确有些是事情是办不到的，比如绑定80端口，或将数据写到你的应用容器之外的一个任意目录。
Certain things are still not possible, such as binding to port 80, or writing to a random directory outside of your application container.
组件上的每一个端口都将被绑定到适当的角色。
Each of the ports on the component will be bound to the appropriate role.
对于MQJMS绑定，该提供程序提供一个称为侦听器端口的设备进行入站交互。
For MQJMS bindings, the provider provides a facility known as listener ports for inbound interactions.
最后一个内部处理作业是以期望端口号绑定到服务器套接字上。
The last housekeeping job is to bind to a server socket on the desired port number.
AP网卡会被绑定到虚拟化启动之后下一个可用的NDIS端口，该绑定关系将一直保持不变，直到禁用无线承载网络，虚拟化结束为止。
The AP adapter is bound to the next available NDIS port when virtualization starts, and the binding remains the same until virtualization ends when wireless Hosted Network is disabled.
同样，VSTA会被绑定到IHV服务将其初始化后的下一个可用NDIS端口，直到IHV服务将其释放，该绑定关系才会结束。
The VSTA adapter is bound to the next available NDIS port when it is initialized by the corresponding IHV service and the binding remains the same until it is released by the IHV service.
CollaborationUse元素，同端口和角色绑定一起，表现为一个协议验证段。
The CollaborationUse element, together with port and role bindings, represents a contract verification piece.
将会引用这个HTTPR绑定，服务端口地址的定位将是一个HTTPRuri。
Will reference this HTTPR binding, and the service port address location will be an HTTPR uri. For example?
bind普遍遭遇的问题是试图绑定一个已经在使用的端口。
The problem commonly encountered with bind is attempting to bind a port that's already in use.
WSDL服务是许多相关的端口的集合，每个端口都包含一个与特定协议绑定的端口类型，并且在特定的的端点地址上可用。
A WSDL service is a collection of related ports, each of which consists of a port type bound to a particular protocol and available at a particular endpoint address.
换言之，我需要确保我在接口WSDL中选择的绑定包含我已经选择的同一个端口(在上面的代码片断中)。
In other words, I need to make sure that the binding I choose in the interface WSDL contains the same port I have already chosen (in the code snippet above).
另外，还有一个新的WSDL编辑器和校验器，为查看和管理WSDL端口、绑定、消息和服务以及遵从ws - I的工具提供了一个基于组件的面板。
In addition, there is a new WSDL Editor and Validator providing a panel based component for viewing and administering WSDL ports, binding, messages, and services, as well as WS-I conformance tools.
这意味着迁移只生成一个BPEL，即使一个端口被绑定到不同场景。
This means that the migration generated one BPEL, even if there is one port bind with different scenarios.
当然将会分别使用一个新绑定、一个新服务和一个新端口，如图21、 图22 和 图23 所示。
There will of course be a new binding, a new service and a new port, as shown in Figure 21, Figure 22, and Figure 23 respectively.
一个是一个端口集，而代表了在特定端点进行特定绑定的可用性。
A is modeled as a collection of ports, where a represents the availability of a particular binding at a specific end-point.
您可以使用bindapi函数来绑定一个地址(一个接口和一个端口)到一个套接字端点。
You can use the bind API function to bind an address (an interface and a port) to a socket endpoint.
找到空闲端口的便利方法是传递一个null地址，它会自动将套接字绑定到本地主机地址，并使用空闲的临时端口。
A convenient way to find a free port is to pass in a null address, which automatically binds the socket to the local host address and USES a free ephemeral port.
一旦创建了完成端口，通过调用CreateIoCompletionPort函数可以将一个套接字和完成端口进行绑定，像下面的方法。
Once a completion port is created, the association of a socket with the completion port can be done by calling the function CreateIoCompletionPort in the following way.
最后我们使用以下代码，并将其跟一个端口绑定起来，通过几个浏览器来访问这个程序了，你还能看到用户数量的增长。
Then finally we use it, and bind to a port! That's all there is to it, visit the app in a few browsers and you'll see the count increase.
端口号为0意味着系统在绑定操作时选择一个临时端口。
A port number of zero will let the system pick up an ephemeral port in a bind operation.
我们需要启用端口6444以接受SSL通信，并通过在该端口上定义一个新的虚拟主机将其绑定到我们的服务。
We need to enable port 6444 to accept SSL communication and bind it to our service by defining a new virtual host on that port.
我们需要启用端口6444以接受SSL通信，并通过在该端口上定义一个新的虚拟主机将其绑定到我们的服务。
We need to enable port 6444 to accept SSL communication and bind it to our service by defining a new virtual host on that port.
应用推荐