Downside To Extjs "iframe Architecture" (should I Refactor To Mvc Pattern?)

I have an existing intranet webapp (solely internal) built with ExtJS using an 'iframe architecture', i.e. it has a top menu and a tabpanel on an index page and about 30 other sepa

Solution 1:

Unfortunately I don't have project similar to what you have handy so I can't test it myself but here are my 2c... :)

1. I do think each page will initiate its own copy of ExtJs framework but I think it only has an affect on CPU and memory usage. Network traffic should not be very different as core ExtJs files will be cached.

2. I do recommend to check out network traffic while running this app as you will see how exactly browser handles all this. You might want to add some additional logic into core ExtJs functions to confirm if framework is in fact instantiated several times.

3. If end users experience some performance issues - it might be very good point to justify re-factoring. Otherwise it's kind of hard. Unless of course you have some plans of expanding functionality in near future and planning on continue working on this application.