- Sort Score
- Result 10 results
- Languages All
Results 1 - 9 of 9 for mhevery (0.23 sec)
-
docs/en/docs/tutorial/response-model.md
In this case, it might not be a problem, because it's the same user sending the password. But if we use the same model for another *path operation*, we could be sending our user's passwords to every client. !!! danger Never store the plain password of a user or send it in a response like this, unless you know all the caveats and you know what you are doing. ## Add an output model
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu Apr 18 19:53:19 GMT 2024 - 17.9K bytes - Viewed (0) -
docs/en/docs/alternatives.md
These features are what Marshmallow was built to provide. It is a great library, and I have used it a lot before. But it was created before there existed Python type hints. So, to define every <abbr title="the definition of how data should be formed">schema</abbr> you need to use specific utils and classes provided by Marshmallow. !!! check "Inspired **FastAPI** to"
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu Apr 18 19:53:19 GMT 2024 - 23.2K bytes - Viewed (0) -
docs/en/docs/deployment/concepts.md
If you have an API that does a comparable amount of computations every time and you have a lot of clients, then the **CPU utilization** will probably *also be stable* (instead of constantly going up and down quickly). ### Examples of Replication Tools and Strategies
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu May 02 22:37:31 GMT 2024 - 18K bytes - Viewed (0) -
docs/en/docs/advanced/custom-response.md
For large responses, returning a `Response` directly is much faster than returning a dictionary.
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu Apr 18 19:53:19 GMT 2024 - 11.7K bytes - Viewed (0) -
docs/en/docs/async.md
So, during that time, the computer can go and do some other work, while "slow-file" 📝 finishes. Then the computer / program 🤖 will come back every time it has a chance because it's waiting again, or whenever it 🤖 finished all the work it had at that point. And it 🤖 will see if any of the tasks it was waiting for have already finished, doing whatever it had to do.
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu Apr 18 19:53:19 GMT 2024 - 23K bytes - Viewed (0) -
docs/en/docs/advanced/settings.md
Reading a file from disk is normally a costly (slow) operation, so you probably want to do it only once and then re-use the same settings object, instead of reading it for each request. But every time we do: ```Python Settings() ``` a new `Settings` object would be created, and at creation it would read the `.env` file again. If the dependency function was just like: ```Python
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu May 02 22:37:31 GMT 2024 - 15.7K bytes - Viewed (0) -
docs/en/docs/tutorial/sql-databases.md
* But if you added more code to the middleware that had a lot of <abbr title="input and output">I/O</abbr> waiting, it could then be problematic. * A middleware is run for *every* request. * So, a connection will be created for every request. * Even when the *path operation* that handles that request didn't need the DB. !!! tip
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu Apr 18 19:53:19 GMT 2024 - 29.6K bytes - Viewed (0) -
docs/en/data/github_sponsors.yml
url: https://github.com/sadikkuzu - login: Mehver avatarUrl: https://avatars.githubusercontent.com/u/75297777?u=dcd857f4278df055d98cd3486c2ce8bad368eb50&v=4 url: https://github.com/Mehver - login: rwxd avatarUrl: https://avatars.githubusercontent.com/u/40308458?u=cd04a39e3655923be4f25c2ba8a5a07b3da3230a&v=4
Others - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Fri May 03 22:21:11 GMT 2024 - 26.8K bytes - Viewed (0) -
docs/en/docs/deployment/docker.md
Using the cache in this step will **save** you a lot of **time** when building the image again and again during development, instead of **downloading and installing** all the dependencies **every time**. 5. Copy the `./app` directory inside the `/code` directory. As this has all the code which is what **changes most frequently** the Docker **cache** won't be used for this or any **following steps** easily.
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu May 02 22:37:31 GMT 2024 - 34K bytes - Viewed (0)