Searched full:transparently (Results 1 – 25 of 146) sorted by relevance
123456
99 /// Transparently provide more efficient getOperand methods.167 /// Transparently provide more efficient getOperand methods.403 /// Transparently provide more efficient getOperand methods.547 /// Transparently provide more efficient getOperand methods.584 /// Transparently provide more efficient getOperand methods.608 /// Transparently provide more efficient getOperand methods.
70 a new handshake is started then this will be handled transparently by calling74 this will be handled transparently through calling any OpenSSL IO function. For
244 Normally clients and servers will transparently attempt to negotiate the252 Normally clients and servers will transparently attempt to negotiate the269 Normally clients and servers will transparently attempt to negotiate the277 Normally clients and servers will transparently attempt to negotiate the
50 1. This is handled transparently by these functions.
56 transparently with any underlying ENGINE implementation because it uses the
129 a new handshake is started then this will be handled transparently by calling133 this will be handled transparently through calling any OpenSSL IO function. For
275 Normally clients and servers will transparently attempt to negotiate the282 Normally clients and servers will transparently attempt to negotiate the297 Normally clients and servers will transparently attempt to negotiate the304 Normally clients and servers will transparently attempt to negotiate the
108 1. This is handled transparently by these functions.
115 transparently with any underlying ENGINE implementation because it uses the
11 # Route all UDP packets through transparently.
51 * formats transparently. in IMPLEMENT_PEM_rw()182 /* Transparently read in PKCS#3 or X9.42 DH parameters */ in IMPLEMENT_PEM_write()
83 /// Transparently provide more efficient getOperand methods.110 /// Transparently provide more efficient getOperand methods.138 /// Transparently provide more efficient getOperand methods.174 /// Transparently provide more efficient getOperand methods.211 /// Transparently provide more efficient getOperand methods.
4 mechanism that allows for clients to transparently make remote method
14 mechanism that allows for clients to transparently make remote method
56 argument transparently to
40 including the ability to transparently have a mouse pointer superimposed on
51 * rwlock_padalign rwlocks can use the rwlock(9) API transparently without
54 * mtx_padalign mutexes can use the mtx(9) API transparently without
63 * Since POWER ISA 2.07B this is solved transparently
67 then transparently invokes
122 wide string, the object will transparently convert formats
33 copied and transparently passed to the remote side as part of the
44 copied and transparently passed to the remote side as part of the
85 // Subclasses must provide a command object that will be transparently used
17 I/O it can transparently handle SSL connections, unencrypted network