Search Options

Results per page
Sort
Preferred Languages
Advance

Results 131 - 140 of 218 for syntax (0.23 sec)

  1. CREDITS

          boilerplate notice, with the fields enclosed by brackets "[]"
          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.
    Registered: Sun Sep 07 19:28:11 UTC 2025
    - Last Modified: Thu Mar 13 05:29:51 UTC 2025
    - 1.8M bytes
    - Viewed (0)
  2. src/test/java/jcifs/dcerpc/DcerpcBindTest.java

                verify(mockBuffer, times(2)).align(4); // alignment calls
                verify(mockBuffer).dec_ndr_small(); // num results
                verify(mockBuffer).advance(20); // transfer syntax / version
    
                // Verify result was set
                Field resultField = DcerpcMessage.class.getDeclaredField("result");
                resultField.setAccessible(true);
    Registered: Sun Sep 07 00:10:21 UTC 2025
    - Last Modified: Thu Aug 14 05:31:44 UTC 2025
    - 22.7K bytes
    - Viewed (0)
  3. src/main/java/jcifs/smb1/dcerpc/msrpc/lsarpc.java

        /**
         * Private constructor to prevent instantiation of utility class.
         */
        private lsarpc() {
            // Utility class
        }
    
        /**
         * Returns the RPC syntax identifier for LSA RPC interface.
         *
         * @return the RPC syntax string
         */
        public static String getSyntax() {
            return "12345778-1234-abcd-ef00-0123456789ab:0.0";
        }
    
        /**
         * LSA Quality of Service information.
    Registered: Sun Sep 07 00:10:21 UTC 2025
    - Last Modified: Sat Aug 16 01:32:48 UTC 2025
    - 42.5K bytes
    - Viewed (0)
  4. src/main/java/jcifs/dcerpc/msrpc/samr.java

    public class samr {
    
        /**
         * Private constructor to prevent instantiation of utility class.
         */
        private samr() {
            // Utility class
        }
    
        /**
         * Returns the RPC interface syntax UUID and version for SAMR protocol.
         *
         * @return The SAMR interface UUID string
         */
        public static String getSyntax() {
            return "12345778-1234-abcd-ef00-0123456789ac:1.0";
        }
    
    Registered: Sun Sep 07 00:10:21 UTC 2025
    - Last Modified: Sat Aug 16 01:32:48 UTC 2025
    - 23.4K bytes
    - Viewed (0)
  5. src/main/java/jcifs/smb1/dcerpc/msrpc/samr.java

    public class samr {
    
        /**
         * Private constructor to prevent instantiation of utility class.
         */
        private samr() {
            // Utility class
        }
    
        /**
         * Returns the RPC interface syntax UUID and version for SAMR protocol.
         *
         * @return The SAMR interface UUID string
         */
        public static String getSyntax() {
            return "12345778-1234-abcd-ef00-0123456789ac:1.0";
        }
    
    Registered: Sun Sep 07 00:10:21 UTC 2025
    - Last Modified: Sat Aug 16 01:32:48 UTC 2025
    - 23.1K bytes
    - Viewed (0)
  6. LICENSE

          boilerplate notice, with the fields enclosed by brackets "{}"
          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.
    Registered: Thu Sep 04 15:34:10 UTC 2025
    - Last Modified: Thu Jun 14 07:45:22 UTC 2018
    - 11.1K bytes
    - Viewed (0)
  7. LICENSE

          boilerplate notice, with the fields enclosed by brackets "[]"
          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.
    Registered: Fri Sep 05 09:05:11 UTC 2025
    - Last Modified: Tue Nov 22 19:44:46 UTC 2016
    - 11.1K bytes
    - Viewed (0)
  8. LICENSES/LICENSE

          boilerplate notice, with the fields enclosed by brackets "[]"
          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.
    Registered: Fri Sep 05 09:05:11 UTC 2025
    - Last Modified: Fri May 08 04:49:00 UTC 2020
    - 11.3K bytes
    - Viewed (0)
  9. LICENSES/vendor/github.com/NYTimes/gziphandler/LICENSE

          boilerplate notice, with the fields enclosed by brackets "[]"
          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.
    Registered: Fri Sep 05 09:05:11 UTC 2025
    - Last Modified: Wed Feb 03 21:57:36 UTC 2021
    - 11.2K bytes
    - Viewed (0)
  10. LICENSES/vendor/github.com/container-storage-interface/spec/LICENSE

          boilerplate notice, with the fields enclosed by brackets "{}"
          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.
    Registered: Fri Sep 05 09:05:11 UTC 2025
    - Last Modified: Fri May 08 04:49:00 UTC 2020
    - 11.3K bytes
    - Viewed (0)
Back to top