I now want a product that general idea is that,
A server,
There are many clients: WinForm, Web, IOS, Android, WP8, and supporting GOOGLE account verification, also open API for third parties to develop.
In fact, this framework is currently the world there are many, such as GOOGLE, Amazon, Apple are such practices.
I do not know what such a system should be chosen technology.
My initial thought follows:
1, if you want to fit so many clients, this at least use JSON data format or XML, JSON lighter view, should be the preferred JSON
2, support GOOGLE account verification, it should be OpenID technology; support open API, it should be OAuth2.0 technology, so should reference DotNetOpenAuth
3, for the service side of the technology selection is the most tangled, WCF fact, I am most familiar, but the client when the first connection is very slow, so I think that WCF is not suitable;
WCF Data Service data types because it is open, I think an open database structure is not a good thing out, I saw GOOGLE, Apple did not open out, moreover full with EF, I think controlling a single field is not flexible (I may be right EF understand enough), so I think it is not suitable for WCF DATA SERVICE
Excluded from the above two, only ASP.NET WEB API Microsoft platform, this is a new out of something, I see only go HTTP, very lightweight, have not used, do not know ASP.NET WEB API can not afford such a great pressure, or it is appropriate to do this kind of system?
This is just my personal opinion, it may not described, please know that Friends of the altar gets advice, thank you very much!
A server,
There are many clients: WinForm, Web, IOS, Android, WP8, and supporting GOOGLE account verification, also open API for third parties to develop.
In fact, this framework is currently the world there are many, such as GOOGLE, Amazon, Apple are such practices.
I do not know what such a system should be chosen technology.
My initial thought follows:
1, if you want to fit so many clients, this at least use JSON data format or XML, JSON lighter view, should be the preferred JSON
2, support GOOGLE account verification, it should be OpenID technology; support open API, it should be OAuth2.0 technology, so should reference DotNetOpenAuth
3, for the service side of the technology selection is the most tangled, WCF fact, I am most familiar, but the client when the first connection is very slow, so I think that WCF is not suitable;
WCF Data Service data types because it is open, I think an open database structure is not a good thing out, I saw GOOGLE, Apple did not open out, moreover full with EF, I think controlling a single field is not flexible (I may be right EF understand enough), so I think it is not suitable for WCF DATA SERVICE
Excluded from the above two, only ASP.NET WEB API Microsoft platform, this is a new out of something, I see only go HTTP, very lightweight, have not used, do not know ASP.NET WEB API can not afford such a great pressure, or it is appropriate to do this kind of system?
This is just my personal opinion, it may not described, please know that Friends of the altar gets advice, thank you very much!
相信自己，坚持下去。