<vendor>
HP's WebQoS product addresses this very problem. OK, we may be
biased, because it is an HP product, but it really does address the
issue of what to do when your web or application server becomes
heavily loaded or response times start to increase at your site. By
granting a "ticket" to "new-comers" during these heavier periods,
customers who are already on the site get the best service possible.
At the same time, the new folks are shown a timer which counts down,
so that they know exactly how long it will be before they are admitted
to the site. While they are waiting, a merchant can show them a nice
apology message, advertisements, promotions, or coupons or give them
other interesting things to do while they wait. For your information,
this product runs on HP-UX, Windows NT, Solaris, and Linux. The website
providing further info on WebQoS is: http://www.hp.com/go/webqos
</vendor>
Mary Leland
HP Enterprise Internet Alliances Lab
Esa Tahtinen wrote:
>
> Hi,
>
> We all are familiar with a bank branch office. Tellers tend to serve one
> customer at a time and occasionally there seems to be a queue of customers
> waiting for service. Recently they have installed queuing systems where each
> customer may take a ticket for him/herself to be served by any teller based in
> the number on the ticket. Sometimes the office may be that full of customers
> that you decide to return there on another time or day. This is how things
> work in real life.
>
> My client asked me why this could not be the situation in their web-bank as
> well. The purpose would be to cut the peaks of the amount of concurrent
> users. They were wondering if there might be any software solution to find out
> the overall load of their web-application and act accordingly. In normal
> situation this 'web-queuing-system' would not do anything. But if there seems
> to be extensive load (certain amount of users, long average response times
> etc.) in the application it might be able to tell the new-comer that the
> service is busy and it may take approximately this and this many
> seconds/minutes to be able to proceed. The system might even give the user a
> 'number ticket' as well.
>
> Some may regard this kind of system as admitting that web-applications may have
> poor service cabability and the problem should be solved using better
> solutions. However, I think some simple 'web-queuing' application might do in
> certain cases.
>
> It might be nice to build this kind of system but my client was wondering if
> something like this would already exist. Has anybody heard about this kind of
> stuff?
>
> Kind Regards,
>
> Esa
>
> ===========================================================================
> To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
> of the message "signoff EJB-INTEREST". For general help, send email to
> [EMAIL PROTECTED] and include in the body of the message "help".
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
