CODEWITHSUNDEEP
oracle-apexoracle-apex-5
Toufiq - Oracle APEX
Toufiq - Oracle APEX

Reputation: 153

Common region for two pages in an 100 page application

I am trying to find an optimal way to implement a common region, common to multiple pages (but not all pages) in a huge multi page application.

I understand the concept of Page 0. Common regions can be included in page 0 and proper server side conditions can be used to stop rendering these regions from rendering in all pages. But my concern is that the server side condition will be evaluated for every page every time the page is loaded whereas those regions are used only in, say, two pages in a 500 page application . Won't that be an overhead on every page?

Please note that the common region has dynamic actions, PL/SQL Code etc like any other region and so including that regions in page template will not be an option.

Please help me figure out an optimal way.

Thanks

Upvotes: 2

Views: 535

Answers (1)

Scott
Scott

Reputation: 5035

There will be an overhead, but if you still with the declarative "low code" options, it's just like another "if" statement, as opposed to code that's interpreted live.

http://www.grassroots-oracle.com/2013/05/performance-of-apex-conditions.html

It will be slow for the same reason we compile plugin code into packages.

http://www.grassroots-oracle.com/2016/04/improving-plsql-performance-in-apex.html

I think you can be confident of application performance on the global page using a condition like this

enter image description here

If you're really concerned, duplicate the component on each page - you only need to do it twice. And it will just be the meta-data, right? Since the PL/SQL would be just an call to a package...?

Upvotes: 2

Related Questions