So, my first CodePlex project is in the air, and it's called Web Service Compression for Compact Framework. I have made the first public released available today, and if you want to take part in further development, just let me know and I'll add you to the project.

This project started with an article called Web Service Compression with .NET CF that focused on standard HTTP 1.1 Compression, and in that article you can find some interesting results from using compression. The main lessons learned was "On small payloads the saving is at least 50%, and on larger payloads, more than 90% compression, and cost saving, can be achieved. When it comes to performance, the tests show that for small payloads, we have to pay a performance penalty of about 20%, but for larger payloads, we actually get a performance win of about 50%". The idea was developed further in the article Two-Way .NET CF Web Service Compression when the idea of also compressing the requests from the WM device was introduced. The approach used SOAP Extensions, and that is still true for the code in the new CodePlex project.

The fact that compression is now included in CF means that I had to say goodbye to an old and dear friend - SharpZipLib (many thanks, Mike Krüger and the rest of the team). I have used this library in numerous projects through the years, and it has served me very well. The best thing with saying bye was, when converting to the System.IO.Compression namespace, that only two lines of code needed change.

I think that a future direction for this project could be to support WCF services, and as there are several ways to approach that, I was thinking about behaviors...