I just set up a little sample-project with some basic code to create a MVC-App which shows some static data that is received from Ext-Direct with PHP (see the attached ZIP-File for the full source-code):

constructor : function(config) {// The direct-handler-function needs to be applied in the constructor because if we'd do it in the config // there would be errors after deployment of the app (see http://www.sencha.com/forum/showthread.php?196544-MVC-direct-proxy-and-load-order)Ext.applyIf(this.proxy, {directFn: Users.getAllUsers});

Another solution is to define a custom direct that proxy, that stores function references as strings, and tries to parse api functions on request. I wonder which method is better/faster?

Thanks! Finally I have Ext Direct wired up.

I can't believe how much time I have wasted attempting to get Ext Direct to work. I really don't understand Sencha's position on this, should we not be using Ext.application({}) as recommended...? Since there doesn't appear to be a way (out of the box) to get Ext Direct to work without extending the framework as suggested by HriBB.

I was simply going around in circles either resulting in the method being unresolved or directCfg being unresolved. Crazy!

It makes more sense to define the remoting methods as Strings anyhow, especially when using an IDE that attempts to resolve function / object instances in the project.

In 4.2, this problem is solved: Direct proxy API functions are resolved at first call attempt instead of construction time.

And hopefully for Touch 2.2 as well?

A security feature wish of mine is that I use use plain AJAX or whatever to do login authentication and then only permit loading the Direct RPC API once authenticated. This obviously requires delayed binding to stores which hopefully this recent fix will now support (right?).