Refactored and added Web API 2.2 support.

The library has now been refactored heavily and support for WebAPI 2.2 has been added. The library is hence renamed to Protobuf.Services.

Note that WCF version of the library is production tested, however WebAPI is not, expect a production tested version of WebAPI by Feb 2016.

Binaries will now be distributed via Nuget, check below for links:

1. For WCF host and clients: ProtoBuf.Services.WCF (https://www.nuget.org/packages/ProtoBuf.Services.WCF/)
2. For WebAPI host: ProtoBuf.Services.WebAPI (https://www.nuget.org/packages/ProtoBuf.Services.WebAPI/)
3. For WebAPI client: ProtoBuf.Services.WebAPI.Client (https://www.nuget.org/packages/ProtoBuf.Services.WebAPI.Client/)

ReaderQuotas and TCP transport (experimental)

Added reader quota configuration, use it as you would for any other.

Aded TCP transport, all existing test cases pass, however TCP transport is not production tested, hence the "experimental" remark. Unless you can test well I suggest using the http transport.

V1.0.0.0

Production tested version.

You can now safely utilize this in your production workloads! Do check out the project's wiki for performance stats, setup instructions etc.

v0.9.1-beta.2

This version has some critical bug fixes over the previous version.

Tested with actual services, however not production tested yet, hence beta version.

Expect an actual release by end of the year after the code has been production tested.

Features:

1. ProtoBuf serialization in the channel without any drawbacks that come with using protoBuf in services.
2. Compression at a binding level with overriding capability at an operation level.
3. Choose compression between gzip, deflate & Lz4.
4. Lz4 is the best by far, make sure the client also has reference to the Lz4 assembly though.

First Release - Beta

Tested with actual services, however not production tested yet, hence beta version.

Expect an actual release by end of the year after the code has been production tested.

Features:

1. ProtoBuf serialization in the channel without any drawbacks that come with using protoBuf in services.
2. Compression at a binding level with overriding capability at an operation level.
3. Choose compression between gzip, deflate & Lz4.
4. Lz4 is the best by far, make sure the client also has reference to the Lz4 assembly though.