lidavidm commented on PR #43632: URL: https://github.com/apache/arrow/pull/43632#issuecomment-2285097739
Before I dive into the details of the proposal (thanks Weston for all the feedback!) I'll note that gRPC has both models: - a lower-level pull based model where the consumer creates a reactor and pushes operations/polls for completion (so more like the epoll model, less like the Rust Waker model), which for a long time was the only async API - a callback-based model that wraps the pull-based model, which was added later for ease of use. It might be worthwhile to consider similar wrapping in our case. Also, it might be worth considering what exactly is easy/efficient to implement for different use cases. I think ADBC drivers written in Go, for instance, would probably not adapt to the pull based model well, since Go doesn't really want or need to give you that much control, but ones written in Rust or C++ would adapt much better. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: github-unsubscr...@arrow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
