I have a prototype using Ext.Direct, so after using it I understand better what it does for me.
In some cases, it complain on the client side that I didn't provide the right number of arguments, and it batching my AJAX requests when many are done at the same time, like in the initialization of my UI.
Using JSON directly without Ext.Direct is quite easy in both Java Spring, and .NET MVC.
The value of validation of the number of arguments is low. My server would tell me anyway. So it seems the only value is the batching of requests.
Forget about it. Open standards like JSON-RPC or XML-RPC for external interfaces mean easy migration between platforms and solutions. If they adhere to standards, it will be quite easy to migrate to ExtJS competitors without significant server side modifications.
@Tut, think this is not fully right.
I tried to implement Ext.direct with Zend_Json_Server which is a standard JSON-RPC implementation.
The stubs Ext.direct is using look really different as Zend_Json_Server generates, and also the response look different.
So I have to write my own Server class from the code shown here: http://www.sencha.com/forum/showthre...-and-php-Video
Also is right that the Ext.data.store property autoSync, set true, seem not to work always.
Actually I am testing out how to implement it in the right way.
Turkiyenin en sevilen filmlerinin yer aldigi xnxx internet sitemiz olan ve porn sex tarzi bir site olan mobil porno izle sitemiz gercekten dillere destan bir durumda herkesin sevdigi bir site olarak tarihe gececege benziyor. Sitenin en belirgin ozelliklerinden birisi de Turkiyede gercekten kaliteli ve muntazam, duzenli porno izle siteleri olmamasidir. Bu yuzden iste. Ayrica en net goruntu kalitesine sahip adresinde yayinlanmaktadir. Mesela diğer sitelerimizden bahsedecek olursak, en iyi hd porno video arşivine sahip bir siteyiz. "The Best anal porn videos and slut anus, big asses movies set..."