"Operação" aqui se refere a um dos "métodos" HTTP.

Um dos:

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

...e os mais exóticos:

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

No protocolo HTTP, você pode se comunicar com cada rota usando um (ou mais) desses "métodos".

---

Ao construir APIs, você normalmente usa esses métodos HTTP para executar uma ação específica.

Normalmente você usa:

import org.mockito.Mock;
import org.mockito.junit.jupiter.MockitoExtension;

/**
 * Test class for SocketInputStream using JUnit 5 and Mockito.
 * Tests the NetBIOS session layer protocol implementation.
 */
@ExtendWith(MockitoExtension.class)
class SocketInputStreamTest {

    /**
     * Creates a NetBIOS session message header.
     * The header format is:

import org.mockito.junit.jupiter.MockitoExtension;

import jcifs.dcerpc.ndr.NdrBuffer;

/**
 * Comprehensive test suite for jcifs.dcerpc.DcerpcBind class.
 * Tests DCE/RPC bind message functionality for MSRPC protocol compliance.
 */
@ExtendWith(MockitoExtension.class)
@DisplayName("DcerpcBind Tests")
class DcerpcBindTest {

    @Mock
    private DcerpcBinding mockBinding;

    @Mock

## 2. Protocol Specification Reference

- **MS-SMB2 Section 2.2.13.2.12**: SMB2_CREATE_REQUEST_LEASE_V2 for directories
- **MS-SMB2 Section 2.2.14.2.12**: SMB2_CREATE_RESPONSE_LEASE_V2 for directories  

        byte[] buffer = new byte[512];
        int headerStart = 0;
        int bodyStart = Smb2Constants.SMB2_HEADER_LENGTH;

        // Write SMB2 header (64 bytes)
        // Protocol ID
        System.arraycopy(new byte[] { (byte) 0xFE, 'S', 'M', 'B' }, 0, buffer, headerStart, 4);
        // Structure size (64)
        SMBUtil.writeInt2(64, buffer, headerStart + 4);
        // Credit charge

 * License along with this library; if not, write to the Free Software
 * Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
 */
package jcifs;

/**
 * Utility class holding several protocol constrants
 *
 * @author mbechler
 *
 *
 * <p>This interface is intended for internal use.</p>
 */
public interface SmbConstants {

    /**
     * Default SMB port number for direct TCP transport.

 * Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
 */

package jcifs.smb1.smb1;

/**
 * Interface defining NT status codes used in SMB1 protocol operations.
 * These status codes are returned by SMB servers to indicate the result
 * of requested operations. The codes follow the Windows NT status code format.
 */
public interface NtStatus {

//  	Content-Type + "\n" +
//  	Date + "\n" +
//  	CanonicalizedProtocolHeaders +
//  	CanonicalizedResource;
//
// CanonicalizedResource = [ SlashSeparator + Bucket ] +
//  	<HTTP-Request-URI, from the protocol name up to the query string> +
//  	[ subresource, if present. For example "?acl", "?location", "?logging", or "?torrent"];
//
// CanonicalizedProtocolHeaders = <described below>

Salah satu dari:

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

...dan operasi lainnya yang unik:

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

Dalam protokol HTTP, anda bisa berkomunikasi ke setiap path menggunakan satu (atau lebih) metode di atas.

---

Ketika membuat API, anda umumnya menggunakan metode HTTP tertentu untuk proses tertentu.

Umumnya menggunakan:

"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: