Tracking issue of missing functionalities in OpenDAL C binding

[xyjixyjixyji]

Currently the C binding supports...

• write
• read
• delete
• stat
• is_exist
• list

The missing functionalities are.... (welcome to add up)

• async support
• check()
• copy()
• rename()
• remove() (remove_all(), remove_via())
• reader()
• writer()
• Future APIs (append (through write_with(...).append(...)), etc.)
  • This may need some discussions on the implementations since the C does not have such concepts as Future.
• presign APIs (I think this could be considered later)

[Xuanwo]

I'm thinking about adding reader and writer so users can control the underlying data operations. I'm not sure if it's much better to have an opendal-cpp instead.

[xyjixyjixyji]

I'm thinking about adding reader and writer so users can control the underlying data operations. I'm not sure if it's much better to have an opendal-cpp instead.

We could have an opendal cpp binding, but cbindgen generates reletively the same library and header files. Hence the implementation is roughly the same.

I mean its possible that the opendal cpp binding need to share the underlying impl of the C binding but it could wrap it in a better way obviously.

[Xuanwo]

We could have an opendal cpp binding, but cbindgen generates reletively the same library and header files. Hence the implementation is roughly the same.

I'm thinking about cxx instead. The biggest benefit is that we can use existing types in std, for example std::string and std::vector.

[Xuanwo]

• Future APIs (append(), etc.)

Please note that append has been removed: it's now op.write_with("path", bs).append(true).await

[xyjixyjixyji]

We could have an opendal cpp binding, but cbindgen generates reletively the same library and header files. Hence the implementation is roughly the same.

I'm thinking about cxx instead. The biggest benefit is that we can use existing types in std, for example std::string and std::vector.

Definitely, it would be way better to develop on std containers!

[jiaoew1991]

Can c binding add async support? Only having blocking API, concurrency performance will be a problem.

[xyjixyjixyji]

Can c binding add async support? Only having blocking API, concurrency performance will be a problem.

I would say it is 100% possible to implement this since hyper already does this. But it might take me a while to design and implement this since it is relatively complex in C.

[jiaoew1991]

If supporting async in C bindings is difficult, it would be better to directly provide an async API for C++ bindings. 😄

[asukaminato0721]

• async support

• check() feat(bindings/c): add opendal_operator_check #5851

• copy() feat(bindings/C): Add opendal_operator_rename and opendal_operator_copy #3517

• rename() feat(bindings/C): Add opendal_operator_rename and opendal_operator_copy #3517

• remove() (remove_all(), remove_via()) feat(bindings/c): add opendal_operator_check #5851 (comment)

• reader() feat(binding/c): Add blocking_reader for C binding #3259

• writer() feat(bindings/c): add writer operation for Bindings C and Go #5141