HTMLB vs HTML

[former_member187506]

I have a question related to BSP load times.

Our users have been complaining about poor load time performance during the initial start up of bsp applications.

We have a few custom BSP applications that render lists of data collected from various tables inside our backend. The selection pages for these typically include a drop down for org, and some date parameters.

None of the selection pages include a requirement for back end processing. All of controls on the selection page could be built with straight html or with htmlb logic. We used htmlb controls for our buttons and dropdowns.

We have noticed a performance lag with the initial browser load of the htmlb page over a straight html page with a similar set of selection controls.

We looked at the browser source of the htmlb. There is a fair bit of additional stuff that gets called when using the htmlb option. I suspect the server side compile, processing, subsequent render of data, download of attached javascripts and stylesheets is the reason for the delay relative to html load times.

Taking it a step further, we added all of the header links including style sheet links and javascript source links ( though not all of the control function calls or hidden fields) to an html page and compared the two load times of the this page with a similar htmlb page.

HTML was still seemed to load faster. I would expect this to be the case. Since the html approach requires less server side processing than the htmlb approach.

I have done a fair bit of development server side web development using other technologies. The general rule has been to minimize server side processing where possible to reduce server load. Is this an approach that has been adopted elsewhere when using BSP's?

What is the recommended approach to BSP development? Server side or client side?

Do most developers stick with BSP from end to end in their applications?

Any insight is appreciated.

RM

[Former Member · Accepted solution]

Hi Roger,

Any web application could be a bit slower in starting than in running. BSP is not an exception to that however we could anyway have the option to code instead in HTMB than to use the sophisticated HTMLB.

We have developed several application and I was able to feel the power of HTMLB. There are good reasons to stick to it. It encapsulates the processing logic and makes coding much readable and easy to maintain.

The packing and dispatching of events is simple and easy. As any other business application look and feel should be consistent and with HTMLB it is very easy to handle.

Not even HTMLB we have used XHTMLB, PHTMLB and BTF etc. These are more complex than HTMLB encapsulating much complicate logic but handling is very simple as conmpared to functionality they offer. We can even use some javascript code to enhace and make it a powerfull application. Anyway we can have the same application in HTML and javascript which could offer performance however coding effort and maintainence of application could be deanding then.

Anyway applications are for users and if it needs some optimization then it has to be there. Maybe yo could also try optimizing the SQL part.

Hope that was not very long

Cheers

Ankur

[former_member187506 · Accepted solution]

Ankur:

There was never any thought to giving up on HTMLB, but rather be more judicious in its application.

In a stateless application, should we avoid server side logic for performance reasons when client side will do, if look and feel can be maintained?

[Former Member · Accepted solution]

Hi Roger,

Yes if clent side code could serve the same we could get along with it, however in some cases we might overlook maintainence and code readability.

But anyway it is solving the current issue of performance by making good improvements we can step along.

Cheers

Ankur