Turkiyenin en sevilen filmlerinin yer aldigi porno internet sitemiz olan ve sex tarzi bir site olan 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 siteleri olmamasidir. Bu yuzden iste. Ayrica en net goruntu kalitesine sahip adresinde yayinlanmaktadir.
Gelmiş geçmiş en büyük porno sitemiz olan 2pe de her zaman en kaliteli pornoları sunmayı hedefledik. Diğer video sitemiz olan vuam da ise hd porno ağırlıklı çalışmalara başladık.
I've been trying to get up and running with Ext.direct as it looks like a rather elegant way to get to data via PHP/MySQL. In doing so, I have watched the video "Ext Direct through PHP router" ( http://www.sencha.com/forum/showthre...-and-php-Video ) - which is very helpful.
I have this sample code up and running in my environment and I have also adapted it to an app for testing. However, I can only seem to read in data when I adapt the code to my my test app. I see that the methods get loaded to the proxy.api and I set a listener on my store to listen for remove events - which does indeed fire. But when I look at my network panel in the developer console, I do not see any call to router.php when I call store.remove(). The only reference to router.php is when the store is initially loaded (or when I subsequently call store.load() )
I was not seeing any other calls being made. That is to say that update and create would indeed be in the API, but I did not see a call getting made to them.
I think I've figured it out though. In the example code, the query returns a column 'id', but in my test code I was not using/returning a column 'id'. Once I started returning 'id' from the query calls to destroy started working.
I'm not sure if 'id' is required as part of Ext.direct or not, perhaps I've missed it in the documentation and tutorials - will go back for another look.