From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=unavailable autolearn_force=no version=3.4.4 Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!mx02.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Simon Clubley Newsgroups: comp.lang.ada Subject: Re: Gnoga Latest Updates Date: Mon, 13 Oct 2014 18:28:28 +0000 (UTC) Organization: A noiseless patient Spider Message-ID: References: <13fb4505-4abd-4d5b-b18d-d05aa0a4dcb9@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Injection-Date: Mon, 13 Oct 2014 18:28:28 +0000 (UTC) Injection-Info: mx02.eternal-september.org; posting-host="f1aadc170ab4f50a455c7ea7b8ba0990"; logging-data="2217"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1//izIHzfy6iaQlDSgj85DgaeTvvu2Futc=" User-Agent: slrn/0.9.9p1 (Linux) Cancel-Lock: sha1:1DVU+f1rubVLe2Pixmzi5nnx4EM= Xref: news.eternal-september.org comp.lang.ada:22425 Date: 2014-10-13T18:28:28+00:00 List-Id: On 2014-10-13, jeremiah.breeden@gmail.com wrote: > > Question: Is there currently or will there be a way to tell when the > user closes the browser window or navigates to a different URL? > > I am using Tutorial 2 as base example for this, but when a user does > the following: > > Starts Tutorial 2 > Opens localhost:8080 > closes the browser Closes the browser completely causing the browser executable to actually exit or just closes the current window ? At this point run netstat and see what state the connection is in. > Reopens localhost:8080 > > they get the error message: Only one connection permitted. > [snip] > > I tried the On_Abort event, but it doesn't seem to call when the > browser closes or you navigate to a different URL. Is there something > I can do. I want this to be as seamless for my users as possible. > This behaviour is potentially browser specific; I could see how a browser may potentially cache connections in case you decide to go back to the page you just left. After you browse to a different URL, check netstat and see if the original connection is still in an ESTABLISHED state or if the browser has actually closed the connection. Simon. -- Simon Clubley, clubley@remove_me.eisner.decus.org-Earth.UFP Microsoft: Bringing you 1980s technology to a 21st century world