/libcore/dalvik/src/main/java/org/apache/harmony/dalvik/ |
NativeTestTarget.java | 21 * class are all effectively no-ops and may be used to test the mechanisms
|
/external/chromium/third_party/libjingle/source/talk/xmpp/ |
xmpplogintask.cc | 191 // Collect together the SASL auth mechanisms presented by the server 192 std::vector<std::string> mechanisms; local 198 mechanisms.push_back(pelMech->BodyText()); 201 // Given all the mechanisms, choose the best 202 std::string choice(pctx_->ChooseBestSaslMechanism(mechanisms, pctx_->IsEncrypted()));
|
saslmechanism.h | 55 // to abort (for mechanisms that do not do challenge-response)
|
/external/smack/src/org/jivesoftware/smack/sasl/ |
SASLMechanism.java | 43 * Base class for SASL mechanisms. Subclasses must implement these methods:
90 String[] mechanisms = { getName() };
local 92 sc = Sasl.createSaslClient(mechanisms, username, "xmpp", host, props, this);
107 String[] mechanisms = { getName() };
local 109 sc = Sasl.createSaslClient(mechanisms, username, "xmpp", host, props, cbh);
|
/libcore/luni/src/main/java/org/xml/sax/helpers/ |
XMLReaderFactory.java | 42 * configuration mechanisms aren't set up. That method should do its 45 * those configuration mechanisms would see it.</p> 90 * support that flexibility, other mechanisms to determine the default
|
/external/chromium/chrome/browser/ui/cocoa/extensions/ |
extension_popup_controller_unittest.mm | 95 // TODO(andybons): Better mechanisms for mocking out the extensions service
|
browser_actions_container_view.h | 21 // provides mechanisms for resizing.
|
/external/chromium/third_party/libjingle/source/talk/examples/login/ |
xmppauth.h | 59 const std::vector<std::string> & mechanisms,
|
/external/e2fsprogs/lib/uuid/ |
uuid_time.3.in | 50 function. It may or may not work with UUIDs created by other mechanisms.
|
/external/smack/src/org/jivesoftware/smack/ |
SASLAuthentication.java | 44 * <p>The server may support many SASL mechanisms to use for authenticating. Out of the box
45 * Smack provides several SASL mechanisms, but it is possible to register new SASL Mechanisms. Use
46 * {@link #registerSASLMechanism(String, Class)} to register a new mechanisms. A registered
48 * the list of supported SASL mechanisms is determined from the {@link SmackConfiguration}. </p>
90 // Register SASL mechanisms supported by Smack
484 * @param mechanisms collection of strings with the available SASL mechanism reported
487 void setAvailableSASLMethods(Collection<String> mechanisms) {
488 this.serverMechanisms = mechanisms;
|
SASLAuthentication.java.orig | 44 * <p>The server may support many SASL mechanisms to use for authenticating. Out of the box
45 * Smack provides several SASL mechanisms, but it is possible to register new SASL Mechanisms. Use
46 * {@link #registerSASLMechanism(String, Class)} to register a new mechanisms. A registered
48 * the list of supported SASL mechanisms is determined from the {@link SmackConfiguration}. </p>
90 // Register SASL mechanisms supported by Smack
484 * @param mechanisms collection of strings with the available SASL mechanism reported
487 void setAvailableSASLMethods(Collection<String> mechanisms) {
488 this.serverMechanisms = mechanisms;
|
BOSHPacketReader.java | 143 if (parser.getName().equals("mechanisms")) { 144 // The server is reporting available SASL mechanisms. Store
|
UserAuthentication.java | 41 * more flexability in the mechanisms used.
|
/external/srtp/crypto/include/ |
xfm.h | 30 * accessing crypto mechanisms.
|
cryptoalg.h | 63 * accessing crypto mechanisms.
|
/external/e2fsprogs/debian/attic/libs/ |
control | 28 have the problems identified with mechanisms commonly in use. 63 have the problems identified with mechanisms commonly in use.
|
/external/eigen/doc/ |
I01_TopicLazyEvaluation.dox | 5 Executive summary: Eigen has intelligent compile-time mechanisms to enable lazy evaluation and removing temporaries where appropriate. 23 For these reasons, Eigen has intelligent compile-time mechanisms to determine automatically when to use lazy evaluation, and when on the contrary it should evaluate immediately into a temporary variable.
|
/external/linux-tools-perf/Documentation/ |
perf-bench.txt | 46 Scheduler and IPC mechanisms. 51 Suite for evaluating performance of scheduler and IPC mechanisms.
|
/external/webkit/Source/WebCore/rendering/ |
RenderOverflow.h | 31 // There are two types of overflow: layout overflow (which is expected to be reachable via scrolling mechanisms) and 32 // visual overflow (which is not expected to be reachable via scrolling mechanisms).
|
/external/wpa_supplicant_8/wpa_supplicant/doc/docbook/ |
wpa_background.sgml | 51 <para>Keys can be managed using two different mechanisms. WPA can 55 "WPA-Personal", respectively. Both mechanisms will generate a
|
/frameworks/base/core/java/android/webkit/ |
WebSettings.java | 205 * controls and gestures. The particular zoom mechanisms that should be used 247 * Sets whether the WebView should use its built-in zoom mechanisms. The 248 * built-in zoom mechanisms comprise on-screen zoom controls, which are 253 * The built-in mechanisms are the only currently supported zoom 254 * mechanisms, so it is recommended that this setting is always enabled. 256 * @param enabled whether the WebView should use its built-in zoom mechanisms 258 // This method was intended to select between the built-in zoom mechanisms 266 * Gets whether the zoom mechanisms built into WebView are being used. 268 * @return true if the zoom mechanisms built into WebView are being used 277 * using the built-in zoom mechanisms. See {@link #setBuiltInZoomControls} [all...] |
/external/apache-xml/src/main/java/org/apache/xml/utils/ |
PrefixResolver.java | 64 * via an external entity reference or if mechanisms such as xml:base have
|
/external/bouncycastle/bcprov/src/main/java/org/bouncycastle/asn1/x509/ |
KeyPurposeId.java | 13 * dod(6) internet(1) security(5) mechanisms(5) pkix(7) 3}
|
/external/chromium/chrome/common/extensions/ |
extension_l10n_util.h | 26 // normal file-based lookup mechanisms. This is used to set the locale inside
|
/frameworks/base/docs/html/guide/topics/providers/ |
content-providers.jd | 53 data, and provide mechanisms for defining data security. Content providers are the standard
|