Skip to Content

code, pre {font-size:100%;}
pre

code
hr

.sapTxtSml {font-size:x-small;}
</style>

Fast


When the browser requests for page, it expects that response comes quickly. The user expects this too. Also the proxies and firewalls expect the quick answer.

This means not only that the web application must be polite and do not make the user wait, but also it means that long processed requests can be timed out[1] by every part of the client-server chain: proxies can cancel the request, browser can cancel it, even the user can just close the browser.


Slow


Let us start from the easiest, but the most important: the User™.

How to make him to wait until the processing is done? Every developer knows: just write(“Please wait…”). Hopefully the User™ reads the message and does everything what is written.

There are many methods for such warning already developed:

For the shortest operations normally the sand-glass cursor is used. For such simple cases there is the . This tag inserts the script which disables all potentially submitting elements (buttons) and switches the cursor into sand-glass mode.


Slower


For the longer operations we use the Loading Page™. Like this:


Loading…


See also much more detailed desciption from Eddy De Clercq.


Still slower


All the decribed above is intended to force the User™ not to cancel the operation. But if the operation takes too long, it will be canceled either by browser or by proxy.
There is no way (I mean normal way) to postpone these timeouts[1]. The only way is to send the answer before the operation is finished.

Unfortunatelly the BSP does not allow to send the response by parts. So, if there is no chance to split the processing into shorter parts, the only way left is the parallel processing. As one option – SAP R/3 allows to start and monitor the background jobs. Unfortunatelly this is out of my knowledge, let the experts describe how to do this.

Conclusion


Question:


My application does the large request to the database. It takes a long time. In some cases I even get the timeout error while loading page. Is there the standard way or the option to postpone the timeout? How to avoid this timeout?

Answer:


No! There is no standard way of solving this problem. You must reconsider the architecture of your application.


Footnotes:

] – Here described the processing timeout. Do not mix it up with the session timeout! The session timeout is the attribute of the server and it means the max time between two requests. Not the time of the request processing.

] – “Tag” means the element from the BSP extension. I refer to the standard BSP extension XHTMLB.

To report this post you need to login first.

8 Comments

You must be Logged on to comment or reply to a post.

  1. Craig Cmehil
    Is it really 1 out 1001? No offense but I do hope that you pack a little bit more in the way of “implementing” things into your next weblogs.

    Otherwise nice reminder for people.

    (0) 
      1. Craig Cmehil
        That might work, but now that it’s in writing you might have a hard time denying it 🙂

        But please in the future include some implementation examples – the weblogs will go much better that way.

        I look forward to reading the next ones.

        (0) 
    1. Brian McKellar
      In many ways I think the BSP community in SDN has been spoiled :). We have seen excellent weblogs, far beyond my wildest dreams, and we have pushed the art of information sharing past all preset boundaries. But, still I remember my first weblog. It was one real big mountain to climb, that first weblog. The other 1000 (counting binary!) were much easier. As such, one must always honour the commitment to step into the community and say I am here, grill me! (Same as Nicola did in the last days!)

      And if Artem should even just do half of those 1000, we are in business. If you should wonder why I say this: his desk stands just across the corridor from mine. It is Artem that is the code smith in the group, having all the impossible problems dumped on this desk to return “done” a few days later.

      As such, I would say the stage fright is now gone. Let us await number 10.

      (Personally I rather liked the formating of the text, especially the footnotes. Must steal an idea or two here!)

      brian

      (0) 

Leave a Reply