Salas de espera generales

Throughout our documentation we refer to ‘catch-all’ Waiting Rooms. This is simply shorthand for a room that matches all URLs on a given domain. It's the default setting for new Waiting Rooms but you can set a room to catch-all status by editing the room and setting URL match to ‘all of <your domain>’.

Catch-all Waiting Rooms are intended to monitor all incoming traffic and be the last line of resort in the case of traffic to your domain exceeding your Ingress Rate. They can be an important safety-net. However, they are also something of a special case, and have some different characteristics to waiting rooms that are more selective on the URLs they match. It may be important to understand these differences if you need to schedule multiple overlapping Waiting Rooms.

Double promotion#

Imaginemos que tienes a la venta las entradas para un gran concierto. Hay poco tráfico de fondo, usuarios habituales que consultan su cuenta y una gran oleada de fans incondicionales que esperan entradas para un concierto concreto. Quieres que el tráfico de fondo sea gestionado por tu «Sala de espera» general, pero sin que se atasque detrás del tráfico de la «Sala de espera» específica del concierto. Pero, ¿qué ocurre cuando tus fans incondicionales pasan de la «Sala de espera» del concierto? Si todos van a consultar su cuenta, simplemente crearás una segunda oleada en la «Sala de espera» general, una segunda cola y un montón de fans enfadados.

To avoid this scenario, catch-all rooms have a special property. When a user is promoted in any specific waiting room on your domain, CrowdHandler automatically and simultaneously gives them promoted status in any catch-all rooms on the same domain. The same is not true for other Waiting Rooms. There's no way we'll allow users to get through a queue for an unpopular act, and achieve promoted status for the much more popular act that everyone else is queuing for.

Can I have more than one catch-all on a domain? And why would I do that?#

You can, but incoming users will only get attached to one, the one with the most recent activation date. Why might you want to do that? Maybe you have a regular catch-all Waiting Room set up how you like it, but you're about to start some planned maintenance on your website. Rather than changing the message on your existing catch-all, you could pre-schedule a catch-all Waiting Room to coincide with your maintenance window, with appropriate messaging, etc., and an ingress rate of 0. At the appointed time, new users will move into the new maintenance window catch-all. When maintenance is finished, you can simply delete the new room, and the original catch-all will resume intercepting users based on your typical and tested settings.