- Sort Score
- Result 10 results
- Languages All
Results 21 - 30 of 611 for compatible (0.14 sec)
-
guava/src/com/google/common/net/InetAddresses.java
* * <p>An "IPv4 compatible", or "compat", address is one with 96 leading bits of zero, with the * remaining 32 bits interpreted as an IPv4 address. These are conventionally represented in * string literals as {@code "::192.168.0.1"}, though {@code "::c0a8:1"} is also considered an * IPv4 compatible address (and equivalent to {@code "::192.168.0.1"}). *
Registered: Fri Nov 01 12:43:10 UTC 2024 - Last Modified: Sat Oct 19 00:26:48 UTC 2024 - 47.1K bytes - Viewed (0) -
docs/en/docs/reference/httpconnection.md
# `HTTPConnection` class When you want to define dependencies that should be compatible with both HTTP and WebSockets, you can define a parameter that takes an `HTTPConnection` instead of a `Request` or a `WebSocket`. You can import it from `fastapi.requests`: ```python from fastapi.requests import HTTPConnection ```
Registered: Sun Nov 03 07:19:11 UTC 2024 - Last Modified: Thu Apr 18 19:53:19 UTC 2024 - 359 bytes - Viewed (0) -
README.md
Guava's Maven group ID is `com.google.guava`, and its artifact ID is `guava`. Guava provides two different "flavors": one for use on a (Java 8+) JRE and one for use on Android or by any library that wants to be compatible with Android. These flavors are specified in the Maven version field as either `33.3.1-jre` or `33.3.1-android`. For more about depending on Guava, see [using Guava in your build].
Registered: Fri Nov 01 12:43:10 UTC 2024 - Last Modified: Tue Sep 24 18:34:38 UTC 2024 - 5.9K bytes - Viewed (0) -
tests/test_tutorial/test_configure_swagger_ui/test_tutorial002.py
), "not used parameters should not be included" assert ( '"syntaxHighlight.theme": "obsidian"' in response.text ), "parameters with middle dots should be included in a JSON compatible way" assert ( '"dom_id": "#swagger-ui"' in response.text ), "default configs should be preserved" assert "presets: [" in response.text, "default configs should be preserved" assert (
Registered: Sun Nov 03 07:19:11 UTC 2024 - Last Modified: Sat Aug 19 19:54:04 UTC 2023 - 1.5K bytes - Viewed (0) -
src/main/webapp/WEB-INF/view/common/admin/head.jsp
<%@page pageEncoding="UTF-8" contentType="text/html; charset=UTF-8"%> <meta content='width=device-width, initial-scale=1, maximum-scale=1, user-scalable=no' name='viewport'> <meta http-equiv="X-UA-Compatible" content="IE=edge"> <link href="${fe:url('/css/admin/bootstrap.min.css')}" rel="stylesheet" type="text/css" /> <link href="${fe:url('/css/admin/font-awesome.min.css')}" rel="stylesheet" type="text/css" />
Registered: Thu Oct 31 13:40:30 UTC 2024 - Last Modified: Wed Feb 12 12:21:50 UTC 2020 - 984 bytes - Viewed (0) -
docs/changelogs/upgrading_to_okhttp_4.md
without changing `.kt` files. With a few small exceptions (below), OkHttp 4.x is both binary- and Java source-compatible with OkHttp 3.x. You can use an OkHttp 4.x .jar file with applications or libraries built for OkHttp 3.x. OkHttp is **not** source-compatible for Kotlin callers, but upgrading should be automatic thanks to Kotlin’s powerful deprecation features. Most developers should be able to use IntelliJ’s _Code
Registered: Fri Nov 01 11:42:11 UTC 2024 - Last Modified: Sun Feb 06 16:58:16 UTC 2022 - 10.9K bytes - Viewed (0) -
src/main/webapp/WEB-INF/orig/view/error/badRequest.jsp
<% try{ %> <html> <head profile="http://a9.com/-/spec/opensearch/1.1/"> <meta charset="utf-8"> <meta name="viewport" content="width=device-width, initial-scale=1"> <meta http-equiv="X-UA-Compatible" content="IE=edge"> <title><la:message key="labels.system_error_title" /></title> <link href="${fe:url('/css/bootstrap.min.css')}" rel="stylesheet" type="text/css" /> <link href="${fe:url('/css/style.css')}" rel="stylesheet"
Registered: Thu Oct 31 13:40:30 UTC 2024 - Last Modified: Sat Oct 26 01:07:52 UTC 2024 - 1.4K bytes - Viewed (0) -
src/main/webapp/WEB-INF/view/error/notFound.jsp
<html> <head profile="http://a9.com/-/spec/opensearch/1.1/"> <meta charset="utf-8"> <meta name="viewport" content="width=device-width, initial-scale=1"> <meta http-equiv="X-UA-Compatible" content="IE=edge"> <title><la:message key="labels.system_error_title" /></title> <link href="${fe:url('/css/bootstrap.min.css')}" rel="stylesheet" type="text/css" /> <link href="${fe:url('/css/style.css')}" rel="stylesheet"
Registered: Thu Oct 31 13:40:30 UTC 2024 - Last Modified: Sat Oct 26 01:07:52 UTC 2024 - 1.3K bytes - Viewed (0) -
src/main/webapp/WEB-INF/view/error/system.jsp
<% try{ %> <html> <head profile="http://a9.com/-/spec/opensearch/1.1/"> <meta charset="utf-8"> <meta name="viewport" content="width=device-width, initial-scale=1"> <meta http-equiv="X-UA-Compatible" content="IE=edge"> <title><la:message key="labels.system_error_title" /></title> <link href="${fe:url('/css/bootstrap.min.css')}" rel="stylesheet" type="text/css" /> <link href="${fe:url('/css/style.css')}" rel="stylesheet"
Registered: Thu Oct 31 13:40:30 UTC 2024 - Last Modified: Sat Oct 26 01:07:52 UTC 2024 - 1.4K bytes - Viewed (0) -
docs/kms/IAM.md
Yes, MinIO will try to transparently migrate any existing IAM data and either stores it in plaintext (no KMS) or re-encrypts using the KMS. > Is this change backward compatible? Will it break my setup? This change is not backward compatible for all setups. In particular, the native Hashicorp Vault integration - which has been deprecated already - won't be supported anymore. KES is now mandatory if a third-party KMS should be used.
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Thu Jan 18 07:03:17 UTC 2024 - 5.3K bytes - Viewed (0)