}

    /**
     * Enumeration representing HTTP methods.
     * <ul>
     *   <li>GET - Requests data from a specified resource.</li>
     *   <li>POST - Submits data to be processed to a specified resource.</li>
     *   <li>PUT - Updates a current resource with new data.</li>
     *   <li>DELETE - Deletes the specified resource.</li>

They tend to require more complex configurations, a message/job queue manager, like RabbitMQ or Redis, but they allow you to run background tasks in multiple processes, and especially, in multiple servers.

     */
    @Override
    public ResponseData doGet(final String uri) {
        return processRequest(uri, true);
    }

    /**
     * Processes a request for the given URI.
     *
     * @param uri the URI to process
     * @param includeContent whether to include content in the response
     * @return the response data

This is the basic idea. But you will probably want to take care of some additional things, like:

* Security - HTTPS
* Running on startup
* Restarts
* Replication (the number of processes running)
* Memory
* Previous steps before starting

     * `ID <= lastGoodStreamId` can only be replayed on a new connection if they are idempotent.
     *
     * @param lastGoodStreamId the last stream ID the peer processed before sending this message. If
     *     [lastGoodStreamId] is zero, the peer processed no frames.
     * @param errorCode reason for closing the connection.
     * @param debugData only valid for HTTP/2; opaque debug data to send.
     */
    fun goAway(

        this.extractorMap = extractorMap;
    }

    /**
     * Creates a new ExtractorBuilder instance.
     *
     * @param in      The input stream to be processed by the extractor.
     * @param params  The parameters to be used by the extractor.
     * @return A new ExtractorBuilder instance.
     */

 * </td>
 * </tr>
 * </table>
 *
 * <p>
 * See <a href="../../../pipes.html">Using jCIFS to Connect to Win32
 * Named Pipes</a> for a detailed description of how to use jCIFS with
 * Win32 Named Pipe server processes.
 *
 */

public class SmbNamedPipe extends SmbFile implements SmbPipeResource {

    private final int pipeType;

    /**
     * Open the Named Pipe resource specified by the url

        assertEquals(0, bytesRead);
        assertNull(response.getInfo());
    }

    @Test
    void testReadDataWireFormat_EmptyBuffer() throws Exception {
        // Test with empty dataCount but decode still processes buffer
        // Note: SmbInfoAllocation.decode() doesn't check len parameter, always reads 20 bytes
        response = new Trans2QueryFSInformationResponse(config, FileSystemInformation.SMB_INFO_ALLOCATION);

   *       can always page it to disk "for free". However, on systems where killing processes
   *       happens all the time in normal conditions (i.e., android) the OS must make a tradeoff
   *       between paging memory and killing other processes - so allocating a gigantic buffer and
   *       then sequentially accessing it could result in other processes dying. This is solvable
   *       via madvise(2), but that obviously doesn't exist in java.

    }

    /**
     * Reads and processes index settings from configuration file.
     *
     * @param fesenType          the search engine type
     * @param indexConfigFile    the path to the index configuration file
     * @param numberOfShards     the number of primary shards
     * @param autoExpandReplicas the auto expand replicas setting
     * @return the processed index settings JSON
     */