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

Using Komsa.Camunda.Api.Client #66

Open
msdiakov1998 opened this issue Aug 17, 2023 · 3 comments
Open

Using Komsa.Camunda.Api.Client #66

msdiakov1998 opened this issue Aug 17, 2023 · 3 comments

Comments

@msdiakov1998
Copy link

Good afternoon.
Would you consider using Komsa.Camunda.Api.Client as httpClient?

@TechnoBerry
Copy link
Owner

Hello!

I apologize for not answering for a long time.

At the moment I have no plans to use other libraries to work with camunda in the library. Using a self-written camunda client in my library has the following advantages:

  • I don't need to maintain an up-to-date version of a dependency on someone's library
  • Users of my library don't get transitive dependencies like Refit, which they may not need

However, I understand that there may be cases in which developers are forced to connect my library and some library that implements clients for the entire camunda API. Could you describe the APIs that you lack in my library?

@msdiakov
Copy link

Hi.
I was unable to modify and add process variables.
Also, sometimes you need to send signals or messages.

@TechnoBerry
Copy link
Owner

I think that sending of signals or messages can be implemented in my library. These APIs look similar to what is really needed in the worker.

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

3 participants