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

Difference between client.call and client.invoke #321

Open
Berdmanfolk opened this issue Mar 20, 2024 · 4 comments
Open

Difference between client.call and client.invoke #321

Berdmanfolk opened this issue Mar 20, 2024 · 4 comments
Assignees
Labels

Comments

@Berdmanfolk
Copy link

Hello @bsrdjan !
Can you please explain in whicn case using client.call and client.invoke ?

Thanks in advance.

@bsrdjan
Copy link
Member

bsrdjan commented Mar 20, 2024

client.invoke is using callback interface and implemented first. client.call has been added later, providing promise interface and client.invoke remained as-is, for backward compatibility. Usage depends on application style. I would recommend client.call, unless callback interface is more appropriate for particular application

@bsrdjan bsrdjan self-assigned this Mar 20, 2024
@Berdmanfolk
Copy link
Author

Thanks @bsrdjan for the quick response.
Please also tell me which version the client.call() can be used with. Now I'm using version 2.7.0 and I don't have such a method.

@bsrdjan
Copy link
Member

bsrdjan commented Mar 20, 2024

but why using 2.7.0 ? It is built with older and not any more supported RFC SDK.

@Berdmanfolk
Copy link
Author

Because I compiled 2.7.0 for nw.js. And at that time the CMake utility was used. Node-gyp utility is currently being used, and I don’t yet know how to compile it for nw.js. Is there any information on how to do this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants