Version 2.3.0

This description contains the changes from 2.1.1 to 2.3.0:

• rewrite the POST data management. The data is now better accessible and support multiple content types. The old properties are now marked as obsolete but still supported. In future releases they will be removed.
  • add support for multipart/form-data POST content type
  • if the POST content is sent with an unknown mime type the data is still accessible in its raw format
  • the POST data is now lazily parsed. Only if a service needs them the data is extracted.
• add a new reader for HTTP requests HttpRequestParser which supports the binary mode. The old HttpHeaderParser works only in text mode and has problems which different text encodings or binary POST content.
  • The HttpRequestParser allows to switch between text mode (reading headers) and binary mode (reading POST content) and to change the encoding if needed.
• WebProgressImportance is now renamed to WebServicePriority. The WebServicePriority is now an enum which spans the whole int32 value range.
• Add Session filter rules to the REST Api handler.
• POST data is no more cleared after deserialization. This was a bug.
• Fix mime type spellings
• Fix type handling of value types in the REST Api handler.
• Fix deadlock in service execution