Feature #105

Traffic throttling

Added by Jon Ferguson about 5 years ago. Updated over 3 years ago.

Status:ClosedStart date:
Priority:NormalDue date:
Assignee:Artur Hefczyc% Done:

100%

Category:-Estimated time:24.00 hours
Target version:tigase-server-5.1.3
Database: Source Code Disclaimer:

Description

Is there a way to throttle or limit messages being sent from users? So, for example, User 'x' can send up to 3 messages in a 10sec interval.

Cheers,
Jon

smime.p7s (2.17 KB) Anonymous, 2011-05-19 12:34 AM

Associated revisions

Revision 9eee9a62
Added by Artur Hefczyc over 3 years ago

Traffic throttling implemented with configuration options described here: http://www.tigase.org/content/initproperties#cm-traffic-throttling. Fixes: #105

Revision 147be590
Added by Artur Hefczyc over 3 years ago

Traffic throttling implemented with configuration options described here: http://www.tigase.org/content/initproperties#cm-traffic-throttling. Fixes: #105

History

#1 Updated by Artur Hefczyc about 5 years ago

  • Tracker changed from Support to Feature
  • Assignee set to Artur Hefczyc
  • Target version set to tigase-server-5.2.0

It is not possible right now. A new plugin, preprocessor could handle this easily though.

#2 Updated by Jon Ferguson about 5 years ago

Hey Artur,

On this point..
1) would the preprocessor just drop the message given to many were being received?
2) another thought I had would be something like.. after hitting a threshold, lowering the priority of the messages from the same Full JID and putting it back in the queue.. or somehow changing the messages for an offending full JID in this way at an earlier point in the workflow. That might be more friendly - a sort of soft throttle.

Does this make sense?

Cheers,
Jon

-----Original Message-----
From: [mailto:]
Sent: Sunday, April 17, 2011 11:12 PM
Subject: [Tigase XMPP Server - Feature #105] Message Throttling?

Issue #105 has been updated by Artur Hefczyc.

Tracker changed from Support to Feature
Assignee set to Artur Hefczyc
Target version set to 5.2.0

It is not possible right now. A new plugin, preprocessor could handle this easily though.
----------------------------------------
Feature #105: Message Throttling?
http://projects.tigase.org/issues/105

Author: Jon Ferguson
Status: New
Priority: Normal
Assignee: Artur Hefczyc
Category:
Target version: 5.2.0

Is there a way to throttle or limit messages being sent from users? So, for example, User 'x' can send up to 3 messages in a 10sec interval.

Cheers,
Jon

#3 Updated by Anonymous about 5 years ago

See comments below:

Issue #105 has been updated by Jon Ferguson.
Hey Artur,
On this point..
1) would the preprocessor just drop the message given to many were being received?

That's a good question. It is really a business decision. Detecting abuse or a problem is one thing
and a half of the job. Handling the case properly is another part. It's up to upper management to
decide what to do. Even if you just drop the packet you would like to know that it happened,
how often, which user is the offender, etc....

2) another thought I had would be something like.. after hitting a threshold, lowering the priority of the messages from the same Full JID and putting it back in the queue.. or somehow changing the messages for an offending full JID in this way at an earlier point in the workflow. That might be more friendly - a sort of soft throttle.

This is a bit dangerous. First of all you may endup with messages reordering for that user.
However, as he is offender we may not care too much. On the other hand if you put the
message back to the beginning of the queue, the queue may get full at some point because
of the traffic generated by offender and packets for other users may get dropped.

As I said this is a business decision.

Artur

#4 Updated by Jon Ferguson about 5 years ago

Thanks,
Jon

-----Original Message-----
From: [mailto:]
Sent: Wednesday, May 18, 2011 3:35 PM
Subject: [Tigase XMPP Server - Feature #105] Message Throttling?

Issue #105 has been updated by Anonymous.

See comments below:

Issue #105 has been updated by Jon Ferguson.
Hey Artur,
On this point..
1) would the preprocessor just drop the message given to many were being received?

That's a good question. It is really a business decision. Detecting abuse or a problem is one thing
and a half of the job. Handling the case properly is another part. It's up to upper management to
decide what to do. Even if you just drop the packet you would like to know that it happened,
how often, which user is the offender, etc....

2) another thought I had would be something like.. after hitting a threshold, lowering the priority of the messages from the same Full JID and putting it back in the queue.. or somehow changing the messages for an offending full JID in this way at an earlier point in the workflow. That might be more friendly - a sort of soft throttle.

This is a bit dangerous. First of all you may endup with messages reordering for that user.
However, as he is offender we may not care too much. On the other hand if you put the
message back to the beginning of the queue, the queue may get full at some point because
of the traffic generated by offender and packets for other users may get dropped.

As I said this is a business decision.

Artur
----------------------------------------
Feature #105: Message Throttling?
http://projects.tigase.org/issues/105

Author: Jon Ferguson
Status: New
Priority: Normal
Assignee: Artur Hefczyc
Category:
Target version: 5.2.0
Database:

Is there a way to throttle or limit messages being sent from users? So, for example, User 'x' can send up to 3 messages in a 10sec interval.

Cheers,
Jon

#5 Updated by Artur Hefczyc almost 4 years ago

  • Estimated time set to 24.00

#6 Updated by Artur Hefczyc over 3 years ago

  • Subject changed from Message Throttling? to Traffic throttling
  • Status changed from New to In Progress

This ticket was originally about message throttling. I have renamed it to a more generic problem traffic throttling. More details how it is implemented now: http://www.tigase.org/content/initproperties#cm-traffic-throttling

#7 Updated by Artur Hefczyc over 3 years ago

  • Status changed from In Progress to Resolved
  • % Done changed from 0 to 100

Applied in changeset tigase-server|commit:9eee9a62a1823490ba2a2d5794934c81ed6fc10d.

#8 Updated by Artur Hefczyc over 3 years ago

Applied in changeset tigase-server|commit:147be59062e1ee9f9a50e6a107a7737274459161.

#9 Updated by Artur Hefczyc over 3 years ago

  • Status changed from Resolved to Closed

#10 Updated by Wojciech Kapcia over 3 years ago

  • Target version changed from tigase-server-5.2.0 to tigase-server-5.1.3

Also available in: Atom PDF