Why would I want to use Bancha?

If you want to use ExtJS/Sencha Touch and CakePHP Bancha is probably the best solution for you. It handles all marshalling, tranformation of data, shares your CakePHP model configurations with Sencha, and does a lot of work for you. Just check out the quick installation guide for more information.

Last update on 2013-02-21 by Roland Schütz.

I have an existing CakePHP application, can I use Bancha here?

Yes, totally. Bancha will perfectly integrate into your existing project, install the Bancha Cake-Plugin an get started working on your new ExtJS- or Sencha Touch Application.

All your original CakePHP pages will work like the are used to.

Last update on 2013-02-21 by Roland Schütz.

Why does Bancha has his own dispatcher?

The decision for a separate dispatcher wasn’t an easy one, but it was the only way we could support the full Ext.Direct spec. Ext.Direct allows us to pack multiple requests into one http request, like [request1, request3, ..]. Cakes dispatcher is a single dispatcher and can’t handle multiple requests since the design expects HTML outputs. So to accomplish our goal of minimizing network latency we had to wrap cakes single dispatcher with an Bancha dispatcher which handles multiple requests and current routing between ExtJS naming and Cakes naming.

A simple example: A app shows a user login, as soon as the user is logged in 9 different stores/individual records get loaded. Using the standard cakephp dispatcher the first 4 requests would be send by the browser (browsers don’t support sending of unlimited requests at the same time), handled and after those the next 4.. everyone with his own latency, etc… With Banchas Multi-Dispatcher this stays one http request serving the data in a wrapped way.

The icing on the cake is here that we can keep both worlds separate and naming always stays by convention. Also some other features, like remote sorting elegantly integrates into Cake.

Last update on 2013-08-15 by Roland Schütz.


Add a comment