### Generate a TypeScript Client with Tags { #generate-a-typescript-client-with-tags }

If you generate a client for a FastAPI app using tags, it will normally also separate the client code based on the tags.

This way, you will be able to have things ordered and grouped correctly for the client code:

<img src="/img/tutorial/generate-clients/image06.png">

In this case, you have:

```
mc admin service restart myminio
```

### Using WebIdentiy API

Client ID can be found by clicking any of the clients listed [here](http://localhost:8080/auth/admin/master/console/#/realms/minio/clients). If you have followed the above steps docs, the default Client ID will be `account`.

```

## Do not Separate Schemas { #do-not-separate-schemas }

Now, there are some cases where you might want to have the **same schema for input and output**.

///

With that you can connect the WebSocket and then send and receive messages:

<img src="/img/tutorial/websockets/image05.png">

## Handling disconnections and multiple clients { #handling-disconnections-and-multiple-clients }

When a WebSocket connection is closed, the `await websocket.receive_text()` will raise a `WebSocketDisconnect` exception, which you can then catch and handle like in this example.

Now we create a `HeroCreate` model, this is the one that will **validate** the data from the clients.

It has the same fields as `HeroBase`, and it also has `secret_name`.

Now, when the clients **create a new hero**, they will send the `secret_name`, it will be stored in the database, but those secret names won't be returned in the API to the clients.

/// tip

But in many cases, you will want to run several worker processes at the same time.

### Multiple Processes - Workers { #multiple-processes-workers }

     * other SMB clients (including other threads making calls into jCIFS)
     * will not be permitted to access the target file and will receive "The
     * file is being accessed by another process" message.
     */
    int FILE_NO_SHARE = 0x00;
    /**
     * When specified as the <code>shareAccess</code> constructor parameter,
     * other SMB clients will be permitted to read from the target file while

import jcifs.internal.smb1.ServerMessageBlock;

/**
 * SMB1 NT Cancel command implementation.
 * Provides functionality to cancel previously issued SMB1 NT transaction commands
 * that are in progress, allowing clients to abort long-running operations.
 *
 * @author mbechler
 */
public class SmbComNtCancel extends ServerMessageBlock {

    /**
     * Constructs an NT cancel command.
     *

 * These events represent different types of cluster state changes that clients
 * can be notified about.
 */
public enum WitnessEventType {
    /**
     * Resource state changed - general resource state modification
     */
    RESOURCE_CHANGE(1),

    /**
     * Client should move to different node - directed failover
     */
    CLIENT_MOVE(2),

    /**

/**
 * Trans2 GetDfsReferral response message for DFS referral queries.
 * This class handles the response from a TRANS2_GET_DFS_REFERRAL request, which returns
 * DFS referral information for redirecting clients to distributed file system targets.
 */
public class Trans2GetDfsReferralResponse extends SmbComTransactionResponse {

    /**
     * Indicates that the referral contains a name list.
     */