Release 7.0.0: Configuration parameters for realtime technology parameterizable requests

[Guest]

Security considerations in the past made it neccessary to limit the maximum number of parameters per http request so OX isn't vulnerable to a Hash Collision DOS attacks. Therefore we have to configure grizzly accordingly:

# Specify the max. number of allowed request parameters
# Default value: 30
com.openexchange.http.grizzly.maxRequestParameters : 30



Further we introduced some new push/realtime features in the backend that was made configurable in case customers want or do not want to use those features.

### Push technology
################################################## ##############################

# Comet is an umbrella term used to describe a technique allowing web browser to
# receive almost real time updates from the server. The two most common
# approaches are long polling and streaming. Long polling differs from streaming
# in that each update from the server ultimately results in another follow up
# request from the client.
# Default value: true
com.openexchange.http.grizzly.hasCometEnabled=true

# Bi-directional, full-duplex communications channels over a single TCP
# connection.
# Default value: false
com.openexchange.http.grizzly.hasWebSocketsEnabled =true