Ability to NOT batch a request?

I have a case where I'm loading a Portal page, and each portlet then goes off and asks for its content from the server. I'm converting this from RemoteComponent to an Ext.Direct based model.

I got it all working but realized that my portlets, which are asking for their content via Ext.Direct methods, are being batched up and sent to the server all at once. This makes sense, to keep server traffic down, and my router can handle it (Evan's .Net router) so it all "works", but it could be detrimental to the Portal experience. If one portlet takes a while to load, it holds up all of the others which could come back immediately.

What I'd like to do is, per call, tell Ext.Direct that I don't want it to batch the call with others. This way, I could tell my portlet calls to all go separately and be handled by the server on their own.

Is there a way to do this already and I'm just missing it? If not, is it something we could discuss and possibly add in? Or, is there a different way I should be handling the portlets in this case? (Yes, I know I can go back to RemoteComponent, but if there's an Ext.Direct way to do it, I'd rather do it that way.)

Ok, I found the "enableBuffer" property on the provider level. I think this is exactly what I need, BUT it would be nice if this were defined on the method level.

I think what I might end up doing is creating multiple providers, one to contain the non-buffered actions and the other to contain everything else. This will be a bit of a pain because I'll have to further modify the router to be able to handle this, but its doable.

Yes, it is definitely a very good idea. I'm thinking it would be okay to let Ext.Direct buffer requests by default unless a request contains an option, that indicates otherwise, like buffered:false. What do you think?