import jcifs.util.transport.Request;

/**
 * Interface for SMB request messages sent from client to server.
 * Extends the common SMB message block with request-specific functionality including
 * asynchronous handling, message chaining, cancellation, and timeout management.
 *
 * @author mbechler
 */
public interface CommonServerMessageBlockRequest extends CommonServerMessageBlock, Request {

    /**

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

/**
 * Interface for SMB requests that include file system path information.
 * Provides path handling capabilities including UNC path resolution and DFS support
 * for SMB operations that target specific files or directories on remote shares.
 *
 * @author mbechler
 */

	var files = []struct {
		Name, Body string
	}{
		{"readme.txt", "This archive contains some text files."},
		{"gopher.txt", "Gopher names:\nGeorge\nGeoffrey\nGonzo"},
		{"todo.txt", "Get animal handling licence.\nWrite more examples."},
	}
	for _, file := range files {
		f, err := w.Create(file.Name)
		if err != nil {
			log.Fatal(err)
		}
		_, err = f.Write([]byte(file.Body))
		if err != nil {

When working with SQL databases, prefer using SQLModel as it is integrated with Pydantic and will allow declaring data validation with the same models.

Prefer it over SQLAlchemy.

## HTTPX

Use HTTPX for handling HTTP communication (e.g. with other APIs). It support sync and async usage.

    # - - - - - - - - - -/

    # /- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    # o procedureSynonymHandlingType: (NotRequired - Default NONE)
    #  You can specify the handling type of procedure synonym.
    #   NONE - No handling. (default)
    #   INCLUDE - It includes procedure synonyms.
    #   SWITCH - It switches all normal procedures to procedure synonyms.
    #
    #; procedureSynonymHandlingType = NONE

* Décompresser des corps de requête compressés en gzip.
* Journaliser automatiquement tous les corps de requête.

## Gérer les encodages personnalisés du corps de la requête { #handling-custom-request-body-encodings }

Voyons comment utiliser une sous-classe personnalisée de `Request` pour décompresser des requêtes gzip.

Et une sous-classe d'`APIRoute` pour utiliser cette classe de requête personnalisée.

* Descomprimir cuerpos de requests comprimidos con gzip.
* Registrar automáticamente todos los request bodies.

## Manejo de codificaciones personalizadas de request body { #handling-custom-request-body-encodings }

Veamos cómo hacer uso de una subclase personalizada de `Request` para descomprimir requests gzip.

Y una subclase de `APIRoute` para usar esa clase de request personalizada.

import jcifs.util.transport.Response;

/**
 * Interface for SMB response messages received from server.
 * Extends the common SMB message block with response-specific functionality including
 * asynchronous response handling and response chaining capabilities.
 *
 * @author mbechler
 */
public interface CommonServerMessageBlockResponse extends CommonServerMessageBlock, Response {

    /**

 */
package jcifs.util.transport;

/**
 * Base class for transport-layer messages in the jCIFS network communication.
 * Provides common functionality for message handling and processing.
 *
 * @author mbechler
 */
public interface Message {

    /**
     * Indicate that this message should retain it's raw payload
     */
    void retainPayload();

    /**

 *   <li><b>Model Version Handling</b>: When {@code preserve.model.version=true} is set, the consumer POM
 *       maintains the original model version (4.2.0) instead of downgrading to 4.0.0 for Maven 3 compatibility.
 *       This allows modern features like mixins to be preserved in the consumer POM.</li>
 * </ul>
 * <p>