Displaying 3 results from an estimated 3 matches for "mistunderstood".
Did you mean:
missunderstood
2004 Aug 06
2
new features request
...St John wrote:
> > > > Another nice feature to add would be a "bandwidth" limit (so just a
> new
> > > > <limit> type entry).
> If you are running icecast2 on linux you can handle bandwidth limitations
> using QoS
> more specificly iproute2.
You mistunderstood me. No, I cannot handle bandwidth limitations using QoS
because QoS will see plain packets while I want to limit per source. And
my limit has to be "functional". If I use QoS to rate-limit my icecast2
then clients will start to get their stream "slower" then the actual
strea...
2004 Aug 06
0
new features request
...; Another nice feature to add would be a "bandwidth" limit (so just
a
> > new
> > > > > <limit> type entry).
> > If you are running icecast2 on linux you can handle bandwidth
limitations
> > using QoS
> > more specificly iproute2.
>
> You mistunderstood me. No, I cannot handle bandwidth limitations using QoS
> because QoS will see plain packets while I want to limit per source. And
> my limit has to be "functional". If I use QoS to rate-limit my icecast2
> then clients will start to get their stream "slower" then the a...
2004 Aug 06
2
new features request
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Fri, 13 Feb 2004, Geoff Shang wrote:
> Mihai RUSU wrote:
>
> > Another nice feature to add would be a "bandwidth" limit (so just a new
> > <limit> type entry).
>
> Problem with this is, what do you do once the limit has been reached? Who
> do you kick? Or do you just not allow anymore listeners?
I