Tobias Metzke-Bernstein
Tobias Metzke-Bernstein
> @tmetzke I agree with Nico's comment [#17672 (comment)](https://github.com/camunda/camunda/issues/17672#issuecomment-2173669698). While the first option is not RESTful it is more intuitive and also used in public APIs (e.g. [GitHub star a...
All REST endpoints have been defined and added to the [C8 REST API endpoint overview](https://docs.google.com/document/d/1rS989EESojWRrCMLH7Nscy1UppbgOanvzVeOljCc_iA/edit#heading=h.t4xwt6arefiz) (links to the first of the job endpoints, the others follow it directly).
## Background * Long polling keeps the client-gateway connection open on each `activateJobs` request for a defined timeout period to look for activatable jobs. * Long polling can be generally...
Thanks, @nathansandi, for this proposal 👍 If @aleksander-dytko considers this a worthwhile addition, I'd ask you to turn this into a fully-fledged technical proposal, adding the following: - The set...
Thanks, @nathansandi, reads a lot better now and is clearer, nice job 👍 Good job with the operators, I like the overview you created ⭐ I noticed the following things:...
Thanks for updating, @nathansandi 👍 > I prefer without $eq to make equality explicit, because many users are familiar with the tradition way to query, and equality would force them...
@steff46, this is a general proposal for all C8 REST endpoints. If accepted and documented in the guidelines, this will be the standard for all search endpoints offering advanced search....
The exact execution also is a product decision, driven by @aleksander-dytko as the general DRI for the C8 REST API. Having the guideline in 8.6, for example, does not imply...
All good, that is the goal for the current state of the guidelines. We need to make clear what needs to be considered for the endpoints for 8.6 if we...
We always strive to build things incrementally. I consider this a base value in the engineering department. Thus, adopting this with priority in one endpoint first (e.g. task search) makes...