Persistent handles (also known as durable handles) allow SMB3 connections to survive network disconnections, server reboots, and client reconnections. This feature is critical for enterprise reliability and seamless failover scenarios.

## 2. Protocol Specification Reference

- **MS-SMB2 Section 2.2.13.2.3**: SMB2_CREATE_DURABLE_HANDLE_REQUEST
- **MS-SMB2 Section 2.2.13.2.4**: SMB2_CREATE_DURABLE_HANDLE_REQUEST_V2

    }

    boolean isResponse() {
        return (flags & FLAGS_RESPONSE) == FLAGS_RESPONSE;
    }

    /*
     * For this packet deconstruction technique to work for
     * other networking protocols the InputStream may need
     * to be passed to the readXxxWireFormat methods. This is
     * actually purer. However, in the case of smb we know the
     * wordCount and byteCount. And since every subclass of

            <option value="$PROJECT_DIR$/platforms/core-runtime/daemon-main" />
            <option value="$PROJECT_DIR$/platforms/core-runtime/daemon-messaging" />
            <option value="$PROJECT_DIR$/platforms/core-runtime/daemon-protocol" />
            <option value="$PROJECT_DIR$/platforms/core-runtime/daemon-server" />
            <option value="$PROJECT_DIR$/platforms/core-runtime/daemon-services" />

        @Test
        @DisplayName("Should handle negative values in buffer")
        void shouldHandleNegativeValuesInBuffer() throws SMBProtocolDecodingException {
            // Given - negative values (treated as unsigned in protocol)
            ByteBuffer buffer = ByteBuffer.allocate(24);
            buffer.order(ByteOrder.LITTLE_ENDIAN);
            buffer.putLong(-1L);
            buffer.putLong(-1L);
            buffer.putInt(-1);

                    return negotiate2(r);
                } else if (r.getDialectRevision() != Smb2Constants.SMB2_DIALECT_0202) {
                    throw new CIFSException("Server returned invalid dialect verison in multi protocol negotiation");
                }

                final int permits = r.getInitialCredits();
                if (permits > 0) {
                    this.credits.release(permits);
                }

 * Explorer. The users credentials with be negotiated using NTLM SSP if
 * the client is Microsoft Internet Explorer.
 */

/**
 * A servlet that provides network browsing capabilities for SMB shares using SMB1 protocol.
 * This servlet allows users to browse SMB network resources through a web interface.
 */
public class NetworkExplorer extends HttpServlet {

    /**
     * Default constructor.
     */

import jcifs.internal.smb1.com.SmbComTreeConnectAndXResponse;
import jcifs.internal.smb2.tree.Smb2TreeConnectResponse;

/**
 * Test class for TreeConnectResponse interface and its implementations.
 * Tests both SMB1 and SMB2 protocol implementations.
 */
@DisplayName("TreeConnectResponse Tests")
class TreeConnectResponseTest {

    @Mock
    private Configuration mockConfig;

    @BeforeEach
    void setUp() {

 * MA 02111-1307, USA
 */

package jcifs.smb1.util;

import java.io.IOException;
import java.util.Date;

/**
 * Encoding and decoding utility class for SMB1 protocol.
 * Provides methods for encoding/decoding various data types in different byte orders.
 */
public class Encdec {

    /**
     * Default constructor for Encdec.
     * This is a utility class with static methods.

"Operación" aquí se refiere a uno de los "métodos" HTTP.

Uno de:

* `POST`
* `GET`
* `PUT`
* `DELETE`

...y los más exóticos:

* `OPTIONS`
* `HEAD`
* `PATCH`
* `TRACE`

En el protocolo HTTP, puedes comunicarte con cada path usando uno (o más) de estos "métodos".

---

Al construir APIs, normalmente usas estos métodos HTTP específicos para realizar una acción específica.

Normalmente usas:

L’une de :

* `POST`
* `GET`
* `PUT`
* `DELETE`

... et les plus exotiques :

* `OPTIONS`
* `HEAD`
* `PATCH`
* `TRACE`

Dans le protocole HTTP, vous pouvez communiquer avec chaque chemin en utilisant une (ou plusieurs) de ces « méthodes ».

---

En construisant des APIs, vous utilisez normalement ces méthodes HTTP spécifiques pour effectuer une action précise.