Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
We are building “The next generation” web site from the start.
at the moment for UI we use EXT and asp.net
we are thinking that the backend should be a wcf service hosted by iis in which the app will get the data from the service. the main reason is to support diffrent tech in the need of changing the UI. my worry is about speed.
please i will thank any input.
Guy
If speed is the main concern, you can take 2 approaches:
Use a JSON based library. If its a simple app without much of logic at UI tier (and most pushed to service), you can make you pages pure HTML with JS support with using libraries like jQuery or EXT as you have already mentioned. The backend service can be a .NET or Java service as all support json natively.
If you are bound to use ASP.NET for multiple considerations, prefer tcp bindings over http bindings (read more about its pros and cons at MSDN. If security is not a big concern, dont use HTTPS or any transport level security.
Ultimately the implementation will depend a lot of the resources you have. If you have folks who are good in JS, then go for the first option. If folks are more comfortable with ASP.NET stick with the 2nd one.