-
-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for Asynchronous Environments? #12
Comments
@dhrumilp15 Typesense backend API is synchronous in nature. For a large number of use cases this is more convenient as you get to know the result of an operation immediately, instead of having to make one more API call to look up the status. The Python client is also synchronous, so when you call a method on the client, it will block until the response arrives or the operation times out. Can you please help me understand how asynchronous operations will be helpful to your use case? That will help us prioritize future work. |
This does not mean that the API itself has to be asynchronous. This means support for asyncio for using the api in asynchronous applications like FastAPI. |
You can take a look at my async library for CouchDB, which is designed in much the same way as yours, but for an async environment: |
I found a project https://github.com/devtud/aio_typesense that does the job. |
I am poking a dead horse, here, but I started my own implementation, based on aio_typesense that I updated and heavily modified. https://github.com/trollfot/typesense_aio Feel free to jump in |
I forked to add async in such a way that it will be easy for me to keep the fork up to date: https://github.com/Quilt-AI/typesense-python This doesn't require many changes to the current codebase. Supporting both at the same time would be slightly more annoying/complicated but definitely doable. Others are welcome to fork or use it. I think |
Description
This is more of a question/enhanchement! Does typesense-python have support for asynchronous environments?
By this I mean:
The text was updated successfully, but these errors were encountered: