- Sort Score
- Result 10 results
- Languages All
Results 51 - 60 of 470 for recommend (0.15 sec)
-
src/main/java/jcifs/smb1/smb1/ACE.java
* To fully understand the information exposed by this class a description * of the access check algorithm used by Windows is required. The following * is a basic description of the algorithm. For a more complete description * we recommend reading the section on Access Control in Keith Brown's * "The .NET Developer's Guide to Windows Security" (which is also * available online). * <p> * Direct ACEs are evaluated first in order. The SID of the user performing
Java - Registered: Sun May 05 00:10:10 GMT 2024 - Last Modified: Fri Mar 22 21:10:40 GMT 2019 - 7.2K bytes - Viewed (0) -
README.md
OkHttp works on Android 5.0+ (API level 21+) and Java 8+. OkHttp depends on [Okio][okio] for high-performance I/O and the [Kotlin standard library][kotlin]. Both are small libraries with strong backward-compatibility. We highly recommend you keep OkHttp up-to-date. As with auto-updating web browsers, staying current with HTTPS clients is an important defense against potential security problems. [We
Plain Text - Registered: Fri May 03 11:42:14 GMT 2024 - Last Modified: Wed Dec 20 23:27:07 GMT 2023 - 6.2K bytes - Viewed (0) -
LICENSES/vendor/github.com/golang/mock/LICENSE
replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives.
Plain Text - Registered: Fri Apr 12 09:05:11 GMT 2024 - Last Modified: Fri May 08 04:49:00 GMT 2020 - 11.2K bytes - Viewed (0) -
LICENSES/vendor/github.com/google/gnostic-models/LICENSE
replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives.
Plain Text - Registered: Fri Apr 26 09:05:10 GMT 2024 - Last Modified: Fri Jun 02 14:34:25 GMT 2023 - 11.2K bytes - Viewed (0) -
LICENSES/vendor/github.com/moby/sys/mountinfo/LICENSE
replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives.
Plain Text - Registered: Fri Apr 26 09:05:10 GMT 2024 - Last Modified: Wed Jun 24 16:39:50 GMT 2020 - 11.2K bytes - Viewed (0) -
LICENSES/vendor/github.com/ishidawataru/sctp/LICENSE
replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives.
Plain Text - Registered: Fri Apr 26 09:05:10 GMT 2024 - Last Modified: Fri May 08 04:49:00 GMT 2020 - 11.2K bytes - Viewed (0) -
LICENSES/vendor/github.com/google/btree/LICENSE
replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives.
Plain Text - Registered: Fri Apr 26 09:05:10 GMT 2024 - Last Modified: Fri May 08 04:49:00 GMT 2020 - 11.2K bytes - Viewed (0) -
LICENSES/vendor/github.com/modern-go/concurrent/LICENSE
replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives.
Plain Text - Registered: Fri Apr 26 09:05:10 GMT 2024 - Last Modified: Fri May 08 04:49:00 GMT 2020 - 11.2K bytes - Viewed (0) -
LICENSES/vendor/github.com/prometheus/common/LICENSE
replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives.
Plain Text - Registered: Fri Apr 26 09:05:10 GMT 2024 - Last Modified: Fri May 08 04:49:00 GMT 2020 - 11.2K bytes - Viewed (0) -
LICENSES/vendor/github.com/go-openapi/jsonpointer/LICENSE
replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives.
Plain Text - Registered: Fri May 03 09:05:14 GMT 2024 - Last Modified: Fri May 08 04:49:00 GMT 2020 - 11.2K bytes - Viewed (0)