Skip to content
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

Bindings checklist #1

Closed
7 of 17 tasks
bryanchriswhite opened this issue Nov 9, 2017 · 3 comments
Closed
7 of 17 tasks

Bindings checklist #1

bryanchriswhite opened this issue Nov 9, 2017 · 3 comments
Assignees

Comments

@bryanchriswhite
Copy link
Owner

bryanchriswhite commented Nov 9, 2017

(checklist copied from node-libstorj issue #15)

These are functions in libstorj/src/storj.h to be bound:

  • int storj_mnemonic_generate(int strength, char **buffer)
  • bool storj_mnemonic_check(const char *mnemonic)
  • int storj_bridge_get_info(storj_env_t *env, void *handle, uv_after_work_cb cb)
  • int storj_bridge_get_buckets(storj_env_t *env, void *handle, uv_after_work_cb cb)
  • int storj_bridge_create_bucket(storj_env_t *env, const char *name, void *handle, uv_after_work_cb cb)
  • int storj_bridge_delete_bucket(storj_env_t *env, const char *id, void *handle, uv_after_work_cb cb)
  • int storj_bridge_list_files(storj_env_t *env, const char *id, void *handle, uv_after_work_cb cb)
  • int storj_bridge_delete_file(storj_env_t *env, const char *bucket_id, const char *file_id, void *handle, uv_after_work_cb cb)
  • int storj_bridge_store_file_cancel(storj_upload_state_t *state)
  • int storj_bridge_store_file(storj_env_t *env, storj_upload_state_t *state, storj_upload_opts_t *opts, void *handle, storj_progress_cb progress_cb, storj_finished_upload_cb finished_cb)
  • int storj_bridge_resolve_file_cancel(storj_download_state_t *state)
  • int storj_bridge_resolve_file(storj_env_t *env, storj_download_state_t *state, const char *bucket_id, const char *file_id, FILE *destination, void *handle, storj_progress_cb progress_cb, storj_finished_download_cb finished_cb)

And additional:

  • int storj_bridge_register(storj_env_t *env, const char *email, const char *password, void *handle, uv_after_work_cb cb)
  • int storj_bridge_get_bucket(storj_env_t *env, const char *id, void *handle, uv_after_work_cb cb)
  • uint64_t storj_util_timestamp()
  • int storj_bridge_get_file_info(storj_env_t *env, const char *bucket_id, const char *file_id, void *handle, uv_after_work_cb cb)
  • int storj_bridge_list_mirrors(storj_env_t *env, const char *bucket_id, const char *file_id, void *handle, uv_after_work_cb cb)
@bryanchriswhite bryanchriswhite self-assigned this Nov 9, 2017
@marcorosa
Copy link
Contributor

Are those the functions to be bound? libstorj offers these apis, so I guess these are the functions that should be bound:

working with buckets and files:
  list-buckets
  list-files <bucket-id>
  remove-file <bucket-id> <file-id>
  remove-bucket <bucket-id>
  add-bucket <name> 
  list-mirrors <bucket-id> <file-id>
  get-bucket-id <bucket-name>

uploading files:
  upload-file <bucket-id> <path>

downloading files:
  download-file <bucket-id> <file-id> <path>

bridge api information:
  get-info

@bryanchriswhite
Copy link
Owner Author

@marcorosa this issue is a duplicate of storj/python-libstorj#1 and was not kept up to date. I've updated it but will close this issue here as the storj repo is where most people should interact with the python-libstorj repo (this is my development fork).

@bryanchriswhite
Copy link
Owner Author

To answer your question, yes; these are the functions to be bound in order for the library to really be considered usable.

bryanchriswhite pushed a commit that referenced this issue Mar 23, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants