Searched refs:endpoints (Results 1 - 14 of 14) sorted by relevance

/macosx-10.9.5/dcerpc-58/dcerpc/idl_compiler/
H A Difspemts.c168 long i, endpoints; local
171 if ((endpoints = ifp->number_of_ports) != 0)
176 endpoints);
177 for (i = 0; i < endpoints; i++)
180 STRTAB_str_to_string(ifp->endpoints[i], &portspec);
220 fprintf(fid, " {%ld, %s}, /* endpoint vector */\n", endpoints,
221 endpoints ? "IDL_endpoints" : "NULL");
H A Dastp_sim.c1734 interface_p->endpoints = NEW (STRTAB_str_t);
1739 interface_p->endpoints =
1740 RENEW (interface_p->endpoints, interface_p->number_of_ports);
1743 (interface_p->endpoints)[i] = endpoint_id;
H A Dast.h744 int number_of_ports; /* Number of protocol/endpoints below */
746 STRTAB_str_t *endpoints; /* Pointer to array of endpoint strings */ member in struct:AST_interface_n_t
H A Dastp_dmp.c553 STRTAB_str_to_string((interface_node_ptr->endpoints)[i],&endpoint);
/macosx-10.9.5/CPANInternal-140/SOAP-Lite-0.69/lib/SOAP/
H A DConstants.pm30 Unless this parameter is set to 1, outgoing Content-Type headers will include specification of the character set used in encoding the message itself. Not all endpoints (client or server) may be able to properly deal with that data on the content header, however. If dealing with an endpoint that expects to do a more literal examination of the header as whole (as opposed to fully parsing it), this parameter may prove useful.
34 The content-type itself for a SOAP message is rather clearly defined, and in most cases, an application would have no reason to disable the testing of that header. This having been said, the content-type for SOAP 1.2 is still only a recommended draft, and badly coded endpoints might send valid messages with invalid Content-Type headers. While the "right" thing to do would be to reject such messages, that isn't always an option. Setting this parameter to 1 allows the toolkit to skip the content-type test.
H A DTransport.pm586 This method uses the same interface as other classes, but makes use of only the endpoint and envelope keys in the hash-table input data. The endpoint key is needed only if the client wishes to switch endpoints prior to sending the message. The message (the value of the envelope key) is inserted into the queue stored in the requestqueue attribute. The client then waits for a reply to the message to appear in the queue stored in the replyqueue attribute.
/macosx-10.9.5/IOKitUser-907.100.13/usb.subproj/
H A DUSBTest.cpp43 printf("%d endpoints\n", nEP);
46 IOUSBEndpoint *ep = intf->endpoints[i];
308 if(ioint->endpoints[i]->direction == kUSBIn &&
309 ioint->endpoints[i]->transferType == kUSBInterrupt) {
310 ep = ioint->endpoints[i];
/macosx-10.9.5/CPANInternal-140/SOAP-Lite-0.715/lib/SOAP/
H A DConstants.pm152 Unless this parameter is set to 1, outgoing Content-Type headers will include specification of the character set used in encoding the message itself. Not all endpoints (client or server) may be able to properly deal with that data on the content header, however. If dealing with an endpoint that expects to do a more literal examination of the header as whole (as opposed to fully parsing it), this parameter may prove useful.
156 The content-type itself for a SOAP message is rather clearly defined, and in most cases, an application would have no reason to disable the testing of that header. This having been said, the content-type for SOAP 1.2 is still only a recommended draft, and badly coded endpoints might send valid messages with invalid Content-Type headers. While the "right" thing to do would be to reject such messages, that isn't always an option. Setting this parameter to 1 allows the toolkit to skip the content-type test.
/macosx-10.9.5/CPANInternal-140/SOAP-Lite_new/lib/SOAP/
H A DConstants.pm153 Unless this parameter is set to 1, outgoing Content-Type headers will include specification of the character set used in encoding the message itself. Not all endpoints (client or server) may be able to properly deal with that data on the content header, however. If dealing with an endpoint that expects to do a more literal examination of the header as whole (as opposed to fully parsing it), this parameter may prove useful.
157 The content-type itself for a SOAP message is rather clearly defined, and in most cases, an application would have no reason to disable the testing of that header. This having been said, the content-type for SOAP 1.2 is still only a recommended draft, and badly coded endpoints might send valid messages with invalid Content-Type headers. While the "right" thing to do would be to reject such messages, that isn't always an option. Setting this parameter to 1 allows the toolkit to skip the content-type test.
/macosx-10.9.5/emacs-92/emacs/lisp/textmodes/
H A Dartist.el71 ;; straight and connected at their endpoints. Vaporizing is inspired
949 ENDPOINT-1 and ENDPOINT-2 are endpoints which are created with
964 ENDPOINT-1 and ENDPOINT-2 are endpoints which are created with
2495 ;; 2 endpoints
3074 (defun artist-vap-find-endpoints-horiz (x y)
3075 "Find endpoints for a horizontal line through X, Y.
3080 (defun artist-vap-find-endpoints-vert (x y)
3081 "Find endpoints for a vertical line through X, Y.
3086 (defun artist-vap-find-endpoints-swne (x y)
3087 "Find endpoints fo
[all...]
/macosx-10.9.5/CPANInternal-140/SOAP-Lite-0.715/
H A DChanges433 + updated tests and examples with new endpoints
/macosx-10.9.5/CPANInternal-140/SOAP-Lite_new/
H A DChanges349 + updated tests and examples with new endpoints
/macosx-10.9.5/CPANInternal-140/SOAP-Lite-0.69/lib/OldDocs/SOAP/
H A DLite.pm388 This is useful for switching endpoints without switching protocols. You should
/macosx-10.9.5/CPANInternal-140/SOAP-Lite_new/lib/OldDocs/SOAP/
H A DLite.pm388 This is useful for switching endpoints without switching protocols. You should

Completed in 290 milliseconds