[ADC-Ext 1.0.5] STA 48 - Invalid feature
-
- Site Admin
- Posts: 214
- Joined: 21 Jul 2009, 10:21
[ADC-Ext 1.0.5] STA 48 - Invalid feature
There is currently no direct way of saying that a feature is invalid... So, to complement STA 45 (feature missing), I suggest adding STA 48 - Invalid feature. flag "FC" is the FOURCC of the invalid feature. If multiple features are invalid, use comma between the features (i.e. FCQWER,ASDF,ZXCV).
-
- Senior Member
- Posts: 100
- Joined: 30 Dec 2008, 14:59
Re: STA 48 - Invalid feature
**like**
-
- Senior Member
- Posts: 328
- Joined: 04 Dec 2007, 07:25
- Location: Bucharest
- Contact:
Re: STA 48 - Invalid feature
What do you mean by invalid feature? Not supported perhaps ?
What if later on somebody makes the addition QWER as extension ?
We need to be able to keep compatibility...
What if later on somebody makes the addition QWER as extension ?
We need to be able to keep compatibility...
Just someone
-
- Senior Member
- Posts: 100
- Joined: 30 Dec 2008, 14:59
Re: STA 48 - Invalid feature
@Pietry:
The context in which I initially mentioned this idea was a discussion about hubs banning features, such as DHT or segmented downloading (see FlipFlip's SEDL feature announcement proposal). Thus, in this context, 'invalid' would mean 'not welcome'.
I guess, to me, this issue only arises because the client is announcing features where action from the hub is not required, but it is announced out of good citizenship. The obvious response from a malicious client would be to simply not report the feature; however, if the hub was used as a conduit for the feature then obviously the hub could add detection capabilities to remove such unwelcome clients.
The context in which I initially mentioned this idea was a discussion about hubs banning features, such as DHT or segmented downloading (see FlipFlip's SEDL feature announcement proposal). Thus, in this context, 'invalid' would mean 'not welcome'.
I guess, to me, this issue only arises because the client is announcing features where action from the hub is not required, but it is announced out of good citizenship. The obvious response from a malicious client would be to simply not report the feature; however, if the hub was used as a conduit for the feature then obviously the hub could add detection capabilities to remove such unwelcome clients.
-
- Site Admin
- Posts: 214
- Joined: 21 Jul 2009, 10:21
Re: STA 48 - Invalid feature
Added as of ADC-Ext 1.0.5.