Windows Communication Foundation vs Sockets, size of client application and metadata

I started to make an application, in which the priority is client application size, smaller is better. I have to retrieve and add some data from/to a server, basic Add(), GetAll(), Delete(int id), and secure connection. I don't know, on which platform, application will be smaller because on wcf for security i would use ssl, on .NET sockets: i don't know how to implem开发者_如何学运维ent security. I am afraid about the size of metadata..

I'm confused..

Regards,

Sergiu.

---

If you don't have server created yet you can check WCF Data Services. It is technology for exposing CRUD operations over some data source (most common is Entity framework on top of SQL server). You will secure data service with HTTPS.

---

Are you implementing the server side code? If so, I would recommend doing this over RESTful HTTP using OpenRasta. OpenRasta is a framework which provides a natural abstraction for implementing the common HTTP methods POST, PUT, GET and DELETE in a RESTful which should map directly to the data operations you describe. IMHO it is much better than any WCF based alternatives and certainly better than re-inventing the wheel and doing this using a low level socket API. As for SSL, this can be used with OpenRasta - see this answer.

On the client side, you can invoke these operations using simple HTTP requests, obviously with the relevant SSL code in place, see this answer for an example of how to do this. Again, since HTTP is used on the server side, this would be much better than using a low level socket API since the protocol (HTTP) is already well defined and abstracted for you (and anyone else wanting to consume the resources).