- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 16 for someMap (0.21 sec)
-
guava-tests/test/com/google/common/base/AndroidIncompatible.java
* configurations, and there's always the potential that something will go wrong. It * <i>probably</i> won't, since the deps are needed only in tests (and maybe someday in * testlib), but why bother? * <li>Stripping code entirely might help us keep under the method limit someday. Even if it never * comes to that, it may at least help with build and startup times. * </ul> */ @Retention(CLASS)
Java - Registered: Fri Apr 19 12:43:09 GMT 2024 - Last Modified: Fri Jul 07 15:40:13 GMT 2023 - 3.9K bytes - Viewed (0) -
android/guava-tests/test/com/google/common/base/AndroidIncompatible.java
* configurations, and there's always the potential that something will go wrong. It * <i>probably</i> won't, since the deps are needed only in tests (and maybe someday in * testlib), but why bother? * <li>Stripping code entirely might help us keep under the method limit someday. Even if it never * comes to that, it may at least help with build and startup times. * </ul> */ @Retention(CLASS)
Java - Registered: Fri Apr 26 12:43:10 GMT 2024 - Last Modified: Fri Jul 07 15:40:13 GMT 2023 - 3.9K bytes - Viewed (0) -
docs/de/docs/deployment/https.md
### DNS Konzentrieren wir uns nun auf alle tatsächlichen HTTPS-Aspekte. Zuerst würde der Browser mithilfe der **DNS-Server** herausfinden, welches die **IP für die Domain** ist, in diesem Fall für `someapp.example.com`. Die DNS-Server geben dem Browser eine bestimmte **IP-Adresse** zurück. Das wäre die von Ihrem Server verwendete öffentliche IP-Adresse, die Sie in den DNS-Servern konfiguriert haben.
Plain Text - Registered: Sun Apr 28 07:19:10 GMT 2024 - Last Modified: Sat Mar 30 20:16:46 GMT 2024 - 13.5K bytes - Viewed (0) -
docs/en/docs/deployment/https.md
### DNS Now let's focus on all the actual HTTPS parts. First, the browser would check with the **DNS servers** what is the **IP for the domain**, in this case, `someapp.example.com`. The DNS servers would tell the browser to use some specific **IP address**. That would be the public IP address used by your server, that you configured in the DNS servers.
Plain Text - Registered: Sun Apr 28 07:19:10 GMT 2024 - Last Modified: Thu Jan 11 16:31:18 GMT 2024 - 12K bytes - Viewed (0) -
docs/zh/docs/deployment/https.md
这个操作一般只需要在最开始执行一次。 !!! tip 域名这部分发生在 HTTPS 之前,由于这一切都依赖于域名和 IP 地址,所以先在这里提一下。 ### DNS 现在让我们关注真正的 HTTPS 部分。 首先,浏览器将通过 **DNS 服务器** 查询**域名的IP** 是什么,在本例中为 `someapp.example.com`。 DNS 服务器会告诉浏览器使用某个特定的 **IP 地址**。 这将是你在 DNS 服务器中为你的服务器配置的公共 IP 地址。 <img src="/img/deployment/https/https01.svg"> ### TLS 握手开始 然后,浏览器将在**端口 443**(HTTPS 端口)上与该 IP 地址进行通信。
Plain Text - Registered: Sun Apr 28 07:19:10 GMT 2024 - Last Modified: Tue Jan 09 15:38:25 GMT 2024 - 10.6K bytes - Viewed (0) -
docs/ru/docs/deployment/https.md
### DNS Теперь давайте сфокусируемся на работе с HTTPS. Всё начинается с того, что браузер спрашивает у **DNS-серверов**, какой **IP-адрес связан с доменом**, для примера возьмём домен `someapp.example.com`. DNS-сервера присылают браузеру определённый **IP-адрес**, тот самый публичный IP-адрес вашего сервера, который вы указали в ресурсной "записи А" при настройке. <img src="/img/deployment/https/https01.svg">
Plain Text - Registered: Sun Apr 28 07:19:10 GMT 2024 - Last Modified: Wed Apr 03 16:22:47 GMT 2024 - 20.6K bytes - Viewed (0) -
tensorflow/c/c_test.c
if (TF_GetCode(status) != TF_OK) { fprintf(stderr, "TF_CloseWritableFile failed: %s\n", TF_Message(status)); } TF_StringStreamDone(s); TF_KernelBuilder* b = TF_NewKernelBuilder("SomeOp", "SomeDevice", &create, &compute, NULL); TF_RegisterKernelBuilder("someKernel", b, status); TF_DeleteStatus(status); return 0;
C - Registered: Tue Apr 30 12:39:09 GMT 2024 - Last Modified: Wed Apr 24 20:50:35 GMT 2024 - 2.8K bytes - Viewed (0) -
futures/listenablefuture1/src/com/google/common/util/concurrent/ListenableFuture.java
* the beginning, thanks to using different `-source -target` values for compiling our `-jre` and * `-android` "flavors.") * * (We could consider releasing a listenablefuture:1.0.1 someday. But we would want to look into how * that affects users, especially users of the Android Gradle Plugin, since the plugin developers * put in a special hack for us: https://issuetracker.google.com/issues/131431257) */
Java - Registered: Fri Apr 26 12:43:10 GMT 2024 - Last Modified: Mon Jun 26 21:13:41 GMT 2023 - 8K bytes - Viewed (0) -
guava-gwt/pom.xml
could postprocess Collect.gwt.xml to add <skip> lines for all the files that should be covered by testModule.gwt.xml. Maybe I'll try it someday. [*] https://code.google.com/p/google-web-toolkit/wiki/ResourceOracle#When_multiple_PathPrefix_es_have_the_same_path https://code.google.com/p/google-web-toolkit/issues/detail?id=7581
XML - Registered: Fri Apr 26 12:43:10 GMT 2024 - Last Modified: Thu Apr 11 15:00:55 GMT 2024 - 19.8K bytes - Viewed (0) -
docs/ja/docs/deployment/https.md
これはおそらく、最初の1回だけあり、すべてをセットアップするときに行うでしょう。 !!! tip ドメイン名の話はHTTPSに関する話のはるか前にありますが、すべてがドメインとIPアドレスに依存するため、ここで言及する価値があります。 ### DNS では、実際のHTTPSの部分に注目してみよう。 まず、ブラウザは**DNSサーバー**に**ドメインに対するIP**が何であるかを確認します。今回は、`someapp.example.com`とします。 DNSサーバーは、ブラウザに特定の**IPアドレス**を使用するように指示します。このIPアドレスは、DNSサーバーで設定した、あなたのサーバーが使用するパブリックIPアドレスになります。 <img src="/img/deployment/https/https01.svg"> ### TLS Handshake の開始
Plain Text - Registered: Sun Apr 28 07:19:10 GMT 2024 - Last Modified: Mon Sep 25 23:01:57 GMT 2023 - 15.4K bytes - Viewed (0)