-
-
Notifications
You must be signed in to change notification settings - Fork 206
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
[feat] Add some kind of transaction id to API responses #278
Comments
Absolutely! Nice idea :) |
@LordMike Ready 🚀 |
Wouldn't this still require me to compare json objects? :) |
@LordMike If you add an |
Oh.. You're right. 👍 |
That means args are duplicated :D ... |
Yep was to keep back compatibility but I could remove it |
Entirely up to you. I'm satisfied :) |
@robertsLando did this feature disappear? I'm not seeing my original request, on |
I see, the code only sets the origin on errors: If the api call succeeds, its up to the |
@LordMike fixed |
Great :) |
Is your feature request related to a problem? Please describe.
When issuing
getNodes
or similar over MQTT, it can take a long time to get a response. Likewise, when issuing many commands over MQTT, likesetValue
orgetAssociations
, it can be tricky to seperate requests from responses, since the responses all look alike. At least for those with arguments, one can compare the arguments to verify it's what we wanted..Describe the solution you'd like
Add another value to requests, which is optional, and merely echoed back on responses. Like
transaction
,id
ortoken
.Sent:
Response:
This way a client can create their own identifier and match up responses.
Describe alternatives you've considered
I'm currently comparing arguments, but comparing json objects is cumbersome, at least in .NET.
Additional context
N/A
The text was updated successfully, but these errors were encountered: