In the case of IoT i use it a lot devices only look at subscription requests from unsubscribe do users. And I also have component that takes care of devices blocking all messages from non subscribed
Hi Matthew,
Good call. The scenario I have used blocked commands was in a setup where I actually needed configuration instead (setup once).
So for me and the scenarios I have, the ad-hoc command config would be great!.
The only problem I see, is that every server would vary a lot.. and have different policies.
/Steffen
> On 12 Oct 2015, at 23:28, Matthew Wild <mwild1@gmail.com> wrote:
>
> It seems a few people are requesting this. I'd like to understand the use-cases.
>
> For example, if this is something you want to be the default
> behaviour, isn't it better as a deployment configuration? No protocol
> needed.
>
> A per-user configuration would also be possible using ad-hoc commands.
> Again, no extra XEPs needed.
>
> Just throwing things out there, I'd like to understand exactly what people want.
>
> Regards,
> Matthew