Update tokio examples

[juntao]

Explanation

Update docs around networking and tokio examples.

[alabulei1]

Hello, I am a code review bot on flows.network. Here are my reviews of code commits in this PR.

---

Issues and Errors:

• The patches introduce a substantial amount of insertions and deletions, which may pose challenges in reviewing thoroughly, potentially leading to oversight in maintaining code quality and adherence to project goals.
• Applying patches to external crates such as tokio, axum, socket2, reqwest, hyper, mysql_async, and others may introduce dependencies on specific branches, necessitating verification of compatibility and stability.
• Detailed testing of the updated examples for PostgreSQL, Qdrant, Redis, and MySQL database drivers is vital to ensure accuracy and reliability.
• Additional dependencies like anyhow, serde_json, serde, and url are introduced, necessitating the verification of necessity and compatibility within the project setup.
• The transition from the warp to the axum API for asynchronous HTTP servers should be carefully reviewed to assess potential impact on functionality and user requirements.

Important Findings:

• Documentation updates provide clarity and improved guidance for Rust development in the WebAssembly ecosystem, installation requirements, TLS handling, and use of the axum API, enhancing user experience.
• The addition of database client information, examples, and configuration details for PostgreSQL, Qdrant, Redis, and MySQL database drivers enriches the documentation, expanding the scope and utility of the project.
• Application of patches from the WasmEdge community to replace POSIX sockets with WasmEdge sockets and utilization of specific crate versions demonstrate responsiveness to new developments and optimization for performance.
• Inclusion of translated content in Chinese for broader accessibility and reach signifies an inclusive approach to cater to a diverse user base, assuming accuracy in translations and content relevancy.

Recommendations:

1. Thoroughly review the updated documentation, code examples, and configurations to ensure accuracy, relevance, and alignment with project guidelines.
2. Conduct rigorous testing of all examples, especially those relating to database drivers and HTTP service functionalities, to validate correctness and reliability.
3. Verify the compatibility and stability of patched versions of crates and dependencies to prevent unexpected behavior and compatibility issues.
4. Ensure that all changes, including translations and content additions, are well-documented, tested, and maintained for a seamless user experience and efficient development environment.

Details

Commit bb3826ade2337d09d5c9b57d8afcaf4dae7026a5

Key Changes:

1. Updated descriptions and instructions in the documentation files for Rust development in the WebAssembly ecosystem.
2. Updated instructions in the database/my_sql_driver.md file regarding installation requirements and compilation steps, along with the use of TLS.
3. Updated instructions in the http_service/client.md file regarding installation requirements and the use of TLS, especially for macOS.
4. Changed the API from warp to axum in the http_service/server.md file, providing instructions for setting up an HTTP server using the axum API.

Findings:

1. Documentation Updates: The changes in descriptions for the Rust development documentation seem appropriate to enhance clarity and provide better guidance to users.

2. Installation Instructions: The "special notes on networking apps" were added as a reminder, especially for macOS users which is beneficial.

3. TLS Handling: Clear instructions on handling TLS, especially the need for wasi-sdk version of clang for macOS users, have been added, ensuring completeness in the guidance provided.

4. Package Patching: Application of patches developed by the WasmEdge community to replace POSIX sockets with WasmEdge sockets is introduced, along with utilizing specific crate versions for tokio, axum, socket2, and hyper.

5. Transition to axum: The transition from the warp to the axum API is initiated for creating asynchronous HTTP servers, with related example implementations provided.

Recommendations:

1. Ensure that the instructions provided are accurate and up-to-date with the latest changes in the tools and libraries mentioned.
2. Check the compatibility and stability of using patched versions of crates for package patching to avoid unexpected behavior in the application.
3. Review the impact of transitioning from the warp to the axum API, including any potential functionality changes or requirements that users need to be aware of.
4. Confirm that all hyperlink references and code snippets are correctly updated and maintained for a seamless user experience.

Commit 6d3c47ec900c9ab9bfeb658951bdccd9f2654634

Key Changes:

• Added database client information and examples for PostgreSQL, Qdrant, and Redis drivers.
• Added new files for Qdrant database driver documentation.
• Updated the example code for connecting to a PostgreSQL database using tokio-postgres.
• Added configuration information for compiling and patching crates (tokio, tokio-postgres, socket2, and qdrant_rest_client).

Potential Problems:

1. The patch introduces a significant amount of new content (303 insertions) and changes (12 deletions). Ensure that the added content aligns with the project's goals and maintainability.
2. The patch mentions applying patches to external crates (tokio, socket2, reqwest, hyper, and others) which may introduce dependencies on specific branches. Check the compatibility and stability of these branches.
3. The code examples provided are specific to setting up and using the PostgreSQL and Qdrant drivers. Verify that the code examples are accurate and properly formatted.
4. There are additional dependencies listed in the configuration section (anyhow, serde_json, serde, url), ensure they are necessary and compatible with the project's setup.

Overall, ensure that the added content is well-documented, tested, and aligns with the project's guidelines and architecture. Pay close attention to the changes made to dependencies and external crates.

Commit 68b6a726d436b080d0967f518b05d677359546d9

Key Changes:

1. The patch updates several documentation files related to Rust database drivers and HTTP service examples.
2. It adds content to multiple files, primarily focusing on translating English content to Chinese (zh).
3. Configuration changes are made to demonstrate connecting to MySQL databases using Rust and WasmEdge.

Issues/Considerations:

1. The patch introduces a significant number of insertions and deletions (650 insertions, 145 deletions) which may be challenging to review thoroughly.
2. The changes appear to be adding translated content, which could be a positive update for broader accessibility and reach, assuming the translations are accurate.
3. The updated examples may help developers better understand using Rust with MySQL databases, but detailed testing of the examples should be conducted to ensure accuracy.
4. The patch mentions applying patches to the mysql_async and tokio crates, which could introduce dependencies and compatibility issues that need to be carefully evaluated.
5. The patch includes specific configuration changes and code examples related to connecting to MySQL databases, which may provide value to users if documented and explained effectively.

Overall, the patch seems beneficial in terms of content additions and translations, but thorough testing and validation of the code examples are crucial to ensure correctness and compatibility with dependencies.