Jouer au bridge avec Wbridge5 !  
S'enregistrerS'enregistrer  AccueilAccueil  ClassementsClassements  BridgezWbridge5BridgezWbridge5  FAQFAQ  RechercherRechercher  Membres BridgezMembres Bridgez  ConnexionConnexion  
Click on flag to translate !
Traduire ? Clic sur un drapeau
Tous les forums
Liens Directs
Derniers sujets
» Une erreur s'est produite, il faut vous reconnecter
Ven 26 Oct 2018 - 9:53 par jjbridgez

» comment arriver au chelem sur cette donne?
Dim 21 Oct 2018 - 15:08 par kerlouané

» Redemande de l'ouvreur aprés 2/1
Sam 20 Oct 2018 - 9:36 par kerlouané

» acces aux commentaires
Ven 14 Sep 2018 - 13:30 par alibab66

» Changement de mail
Mar 14 Aoû 2018 - 13:32 par joueur00

» Connexion impossible
Mar 22 Mai 2018 - 10:45 par fregoli

» Rapport du mois
Mer 2 Mai 2018 - 6:24 par ardi71

» BW5clés - nouveautés avec WBridge5
Mar 3 Avr 2018 - 19:05 par Maître Fay

» Assemblée Générale
Sam 24 Mar 2018 - 5:50 par Gérard

17ème championnat du monde de bridge ur ordinateur
Jeu 26 Sep 2013 - 4:32 par Gérard
A l’initiative d'Alan Truscott, organisée par la Fédération Mondiale de Bridge (WBF, Président José Damiani) conjointement avec la Fédération américaine (ACBL), sous la Direction d'Alvin …

Commentaires: 0
Objet du site - site purpose
Lun 24 Aoû 2009 - 21:09 par Gérard
(for english see below)
Ce forum est relié à un site qui permet de jouer au bridge en ligne.
Ce site a plusieurs objectifs:
- permettre aux joueurs de jouer un très bon bridge à leur …

Commentaires: 0
Le FORUM Bridgez est né !!
Jeu 20 Aoû 2009 - 9:54 par Admin
Le 25 Août 2009 à 01H23

..........Vive le Bridge !

Bridgez: pour jouer au bridge gratuitement avec Wbridge5 !

Commentaires: 0
Qui est en ligne ?
Il y a en tout 0 utilisateur en ligne :: 0 Enregistré, 0 Invisible et 0 Invité :: 1 Moteur de recherche


Le record du nombre d'utilisateurs en ligne est de 79 le Ven 28 Juil 2017 - 17:38

Résultats par :
Rechercher Recherche avancée
Visites depuis 31/10/2009


 Non compliant browsers for playing on

Voir le sujet précédent Voir le sujet suivant Aller en bas 
Auteur Message


Messages : 276
Date d'inscription : 22/08/2009
Age : 77
Localisation : Paris 14ème

MessageSujet: Non compliant browsers for playing on   Dim 20 Sep 2015 - 6:23

Some browsers, Safari, Internet Explorer 11, Edge, Dolphin do not conform to the standard RFC2616 (HTTP 1.1) This standard specifies that the browser should remain connected during all the time that lasts the session.

To have a look at the standard:
and more precisely:
Citation :
Prior to persistent connections, a separate TCP connection was established to fetch each URL, increasing the load on HTTP servers and causing congestion on the Internet. The use of inline images and other associated data often require a client to make multiple requests of the same server in a short amount of time. Analysis of these performance problems and results from a prototype implementation are available [26] [30]. Implementation experience and measurements of actual HTTP/1.1 (RFC 2068) implementations show good results [39]. Alternatives have also been explored, for example, T/TCP [27].

Persistent HTTP connections have a number of advantages:

     - By opening and closing fewer TCP connections, CPU time is saved
       in routers and hosts (clients, servers, proxies, gateways,
       tunnels, or caches), and memory used for TCP protocol control
       blocks can be saved in hosts.
     - HTTP requests and responses can be pipelined on a connection.
       Pipelining allows a client to make multiple requests without
       waiting for each response, allowing a single TCP connection to
       be used much more efficiently, with much lower elapsed time.
     - Network congestion is reduced by reducing the number of packets
       caused by TCP opens, and by allowing TCP sufficient time to
       determine the congestion state of the network.
     - Latency on subsequent requests is reduced since there is no time
       spent in TCP's connection opening handshake.
     - HTTP can evolve more gracefully, since errors can be reported
       without the penalty of closing the TCP connection. Clients using
       future versions of HTTP might optimistically try a new feature,
       but if communicating with an older server, retry with old
       semantics after an error is reported.
HTTP implementations SHOULD implement persistent connections.
concluding paragraph is:
   HTTP implementations SHOULD Implement persistent connections.

Now when you play 'On the cloud', these browsers automatically disconnect after each server response. It automatically reconnects to post the following query that asks bid or card played by the robot.
This causes several hundred disconnections reconnections to play a tournament!
In general if you do notice anything except where reconnection is not successful and the system seems blocked.

But what happens when reconnecting?

A query posted by a offline browser must first find his way in the forest of computers that make up the Internet, each with a verification of the integrity of data received and eventual reissue them in case of corruption those data.
Once it reaches the server, this later, unaware of who is posting this request, must load into memory a specific program capable of handling all types of possible initial connections including those that will reject because wrong. It then processes the data it finds and extract cookies that will help identify the player.
Finally he examines the list of hundreds of players to find one that might be playing, otherwise it loads him into memory.
When disconnecting, the server frees the memory it no longer needs and signals to the computer's operating system (Windows) that is responsible for managing the memory allocated to a program and prevents other programs are using it. Or Windows rarely reuses the memory thus freed because he does not know a priori which instead will need to reapply for memory allocation.
The result is that the memory used by the server indefinitely swells over time.

While all this is totally unnecessary!

Before the campaign began to ask another browser, the server 'On the cloud' suffered every day 170,000 of these unnecessary connections.
Remember that if this site is free is that it runs on my home computer and not on a paid host server!

I spent a lot of time and energy to identify the problem of the players who remained blocked, create the tool that allows me to measure and identify browsers that do not meet the standard and those who respect it. Then searching the internet if there was a solution to whatever the browser standard is respected.

In vain. I have not found if there was a setting that allowed these browsers to return to operation complies with the standard.
Repeatedly, I addressed to companies that create these browsers to notify them the problem. none has seen necessary to respond to me even not just to acknowledge that.

Unless one know how to correctly configure the browser, I therefore urge to switch browsers to play on 'On the cloud' using Firefox or Chrome that meet the standard and which are free.
Their own playing comfort should find improved.

If we wish to keep the current default browser for other internet activities, Simply create a shortcut to the home page of Bridgez to put on the desktop.
Revenir en haut Aller en bas

Non compliant browsers for playing on

Voir le sujet précédent Voir le sujet suivant Revenir en haut 
Page 1 sur 1

Permission de ce forum: Vous ne pouvez pas répondre aux sujets dans ce forum
Bridgez :: Tous les Forums :: Aide - Help :: J'ai besoin d'aide... -