robot-ranger

maybe im missing something...but isnt this what probe is for?

i think im following you now. the agent could be configured with user-customized topic prefixes. So youre suggesting a topic with payload like the following to inform client apps of...

ok, right. i was expecting to be able to walk the json to Current/Agent by path instead of by name. if that makes any sense. since the name is `Agent.[uuid]`...

TLDR - imo, the agent probe and current should be accessible by name-agnostic path to improve the flexibility of client apps. ETA: it would be nice to be able to...

I cant exclusively subscribe to the agent because my client app may not know the agent uuid and therefore does not know the topic string to subscribe to. The only...

i suppose i could unsubscribe... 🤔

well... i hadnt thought of that; not something we envisioned in our use cases. But that is a good point..

posting in hopes this is a clue... we had this problem before when the agent was creating a unique client connection to the broker for the sink as well as...

when requesting an asset by asset id, how do we tell if that asset id had been previously deleted or not?

oh, i see `removed="true"` in the asset xml element. the issue is `removed=true` gets included in the response to both the first DELETE REST call, and any subsequent DELETE calls...