#### Blocking APIs

Blocking APIs are convenient because you get top-to-bottom procedural code without indirection. Network calls work like regular method calls: ask for data and it is returned. If the request fails, you get a stacktrace right where the call was made.

Blocking APIs may be inefficient because you hold a thread idle while waiting on the network. Threads are expensive because they have both a memory overhead and a context-switching overhead.

 * on an SMB network like one might with Network Neighborhood or Windows
 * Explorer. The users credentials with be negotiated using NTLM SSP if
 * the client is Microsoft Internet Explorer.
 *
 * @deprecated Unsupported
 */
@Deprecated
/**
 * A servlet that provides network browsing capabilities for SMB shares.
 * This servlet allows users to browse SMB network resources through a web interface.
 */

      System.out.println("Response 1 response:          " + response1);
      System.out.println("Response 1 cache response:    " + response1.cacheResponse());
      System.out.println("Response 1 network response:  " + response1.networkResponse());
    }

    String response2Body;
    try (Response response2 = client.newCall(request).execute()) {

     *
     * @throws IOException
     *             if a network error occurs
     */

    @Override
    public int read(final byte[] b) throws IOException {
        return read(b, 0, b.length);
    }

    /**
     * Reads up to len bytes of data from this input stream into an array of bytes.
     *
     * @throws IOException
     *             if a network error occurs
     */

    @Override

- It is now possible to use the service annotation `cloud.google.com/network-tier: Standard` to configure the Network Tier of the GCE Loadbalancer ([#88532](https://github.com/kubernetes/kubernetes/pull/88532), [@zioproto](https://github.com/zioproto)) [SIG Cloud Provider, Network and Testing]

- **Resource Layer**: `SmbResource` interface represents SMB network resources  
- **Protocol Layers**: Separate SMB1 (`jcifs.internal.smb1/`) and SMB2/3 (`jcifs.internal.smb2/`) implementations
- **Authentication**: NTLM, Kerberos, SPNEGO unified subsystem
- **Network Layer**: Transport abstraction, NetBIOS name resolution, session management

### Contributing

    }

    /**
     * Test handling of various path formats
     * This test verifies path parsing without actual network operations
     */
    @Test
    void testPathHandling() throws Exception {
        // Create a test-specific NetworkExplorer that doesn't make network calls
        networkExplorer = new NetworkExplorer() {
            @Override

import jcifs.internal.util.SMBUtil;

/**
 * SMB1 NetServerEnum2 request message for enumerating network servers in a domain or workgroup.
 * This class implements the SMB1 transaction to query for available servers, supporting various
 * server types and filtering options for network browsing functionality.
 */
public class NetServerEnum2 extends SmbComTransaction {

    /**

     * with it.
     *
     * @throws IOException if a network error occurs
     */

    @Override
    public void close() throws IOException {
        file.close();
        tmp = null;
    }

    /**
     * Writes the specified byte to this file output stream.
     *
     * @throws IOException if a network error occurs
     */

    @Override

# Multi-Channel Feature - Detailed Design Document

## 1. Overview

SMB3 Multi-Channel enables the use of multiple network connections between client and server, providing increased throughput, network fault tolerance, and automatic failover capabilities. This feature aggregates bandwidth across multiple NICs and provides seamless failover when network paths fail.

## 2. Protocol Specification Reference