There are currently three implementations of the server side of the ExtJS call:
One is the way of the Web page, his content-type: is application/x-www-form-urlencoded, this kind of application scope is more extensive, as long as can output the server-side environment of the webpage can. ExtJS's official Website example is basically this form, the server side of the environment is php,http://cmsoft.cnblogs.com/is the implementation of this way. NET version, but let me write the dotnet code I do not want to.
One is the webservice way, that is, through XML in the server and the client to pass data, in dotnet This implementation is more complex, and more funny, because the server serialized XML in the client with ASP.net Ajax can be deserialized, but Can be ExtJS call, since I used the EXTJS framework, but also to use ASP.net Ajax framework, really uncomfortable!
Another is the form of WCF, his content-type is Application/json, the principle is based on JSON to pass data on the server side and the client, we have to define the server-side method input, output parameters are JSON form, and secondly, the URL Rewrite and so on (in fact, add an attribute), I think this way to achieve more pleasing to the eye.
Found these two articles at Google http://www.hausertechnologies.com/wordpress/?p=33 and http://www.hausertechnologies.com/wordpress/? P=35 and after my pondering, to figure out some experience, dare not to enjoy alone, so paste out to let the garden like ExtJS and dotnet friends also experience.
I am divided into three sections to describe the EXTJS call WCF series, each section has detailed steps and screenshots, but also provide the source code, if there are people do not understand, go home to see their ears and nose is very large? The development environment is the version of Visual Studio 2008 English RTM and EXTJS 2.0 with no RC, which is currently the latest edition
See more highlights of this column: http://www.bianceng.cnhttp://www.bianceng.cn/webkf/Extjs/