Hi Sajini,
Great!! make sure it works on all scenarios. e.g. from UI and also when
user list subscriptions via API and want to delete them etc.
Thanks
Srinath
On Thu, Dec 3, 2015 at 4:16 PM, Sajini De Silva wrote:
> Hi Srinath,
>
> For durable subscriptions, IP address of the
Hi,
While implementing the feature we have this permission problem w:r:t
permission tree. We want to restrict following two operations
>> subscription browse
>> subscription close (this new feature)
Following are possible permission scenarios
1. One should be able to browse without close
Hi,
As agreed, we implemented the feature. You can only close "local
subscriptions" from management console. You cannot close subscriptions on
any other node.
Management console is displayed as below.
[image: Inline image 1]
Thanks
On Fri, Dec 4, 2015 at 2:57 PM, Hasitha Hiranya
If the user must go to the node where subscription is made to disconnect
the subscription, we might need to give a way for a user to find which node
has what subscriptions.
--Srinath
On Thu, Dec 3, 2015 at 11:36 AM, Ramith Jayasinghe wrote:
> I propose,
> 1) user cant
+1
I would even say stronger "...we MUST give a way..."
Best regards,
Frank
2015-12-03 11:01 GMT+01:00 Srinath Perera :
> If the user must go to the node where subscription is made to disconnect
> the subscription, we might need to give a way for a user to find which node
>
Hi,
There is a feature request that Message Broker should support to forcefully
disconnect a subscriber. This means, server should be able to disconnect
misbehaving subscribers. Server has a control over it.
Steps to do this would be
1. Find a way to disconnect the socket from mina transport
Another point i could think of is, whether we need to warn the user if
attempted to disconnect a subscription which has pre fetched messages, i.e
messages read from the database and which is in the process of writing to
the wire, there might also be subscriptions which has read messages but
have
Hi Hasitha,
We haven't implemented the MQTT UI yet. Therefore IMO its better not to
implement this feature for MQTT for now. We can consider it when
implementing MQTT UI in our major release. WDYT?
Thank you,
Sajini
On Thu, Dec 3, 2015 at 11:19 AM, Hasitha Hiranya wrote:
>
I propose,
1) user cant disconnect consumers in another nodes. ( simplifies the
approach).
2) there need to be a permission around it.
3) it could for any subscriber ( may be lets leave out MQTT for a bit)
whose misbehaving.
On Thu, Dec 3, 2015 at 11:31 AM, Sajini De Silva