| ||||||||
Changed: | ||||||||
< < | Work around abusive users | |||||||
> > | Work around abusive users | |||||||
Changed: | ||||||||
< < | Beginning | |||||||
> > | Beginning | |||||||
Changed: | ||||||||
< < | This work has been proposed by Mark Holliman et we had a first discussion during the Heidelberg IVOA interop in May 2013. | |||||||
> > | This work has been proposed by Mark Holliman et we had a first discussion during the Heidelberg IVOA interop in May 2013 (GWS Session 2). | |||||||
Inputs from Mark Holliman | ||||||||
Changed: | ||||||||
< < | Application Considerations to prevent Abusive User Behaviour | |||||||
> > | Application Considerations to prevent Abusive User Behaviour | |||||||
This page is meant to be a sounding board and general discussion area for the issue of preventing users from knowingly or unknowingly abusing services through VO enabled applications. The topic is of interest both to application developers and data providers. The goal is to make VO enabled applications less likely to enable problematic behaviour by default and to develop possible solutions for data providers that can alleviate or prevent service disruptions. Common examples of "abusive behaviour" include Denial of Service attacks (where a user overloads a service with requests, effectively crashing it), and ... | ||||||||
Changed: | ||||||||
< < | Incident Examples and Proposed Solutions | |||||||
> > | Incident Examples and Proposed Solutions | |||||||
| ||||||||
Changed: | ||||||||
< < | -- MarkHolliman - 2013-09-18 | |||||||
> > | ||||||||
Added: | ||||||||
> > | Inputs from CDSto be completed |
Work around abusive usersBeginningThis work has been proposed by Mark Holliman et we had a first discussion during the Heidelberg IVOA interop in May 2013.Inputs from Mark HollimanApplication Considerations to prevent Abusive User BehaviourThis page is meant to be a sounding board and general discussion area for the issue of preventing users from knowingly or unknowingly abusing services through VO enabled applications. The topic is of interest both to application developers and data providers. The goal is to make VO enabled applications less likely to enable problematic behaviour by default and to develop possible solutions for data providers that can alleviate or prevent service disruptions. Common examples of "abusive behaviour" include Denial of Service attacks (where a user overloads a service with requests, effectively crashing it), and ...Incident Examples and Proposed Solutions
|