Hello Jeremiah, There are several IDs in Gnoga. You mentioned the socket one which is of Integer type that is up to 2**32-1 with my GNAT configuration. An overflow can only occurred in multi-connect application (not single one ;-). In overflow case an exception is thrown and the connection is not established but I guess all others are remaining. As you guessed you need to restart the server, disconnecting existing connections.
There is another ID for DOM objects which is also of Integer type. Same consequence of overflow, no more DOM object is created and I guess the concerned connection may be down, you need to restart the server in both single and multi-connect applications. For now, there is no strategy to cope with the issue, should it have one? Which one? - Long_Long_Integer ;-) - One DOM ID counter per connection - Pool of connection IDs ... Season's Greetings, Pascal. http://blady.pagesperso-orange.fr > Le 24 déc. 2017 à 03:09, Jeremiah Breeden <jeremiah.bree...@gmail.com> a > écrit : > > So I had a question. What happens when your connection ID's max out? How > does Gnoga handle that? Does it stop taking connections and you have to do a > full reset to start over (disconnecting anyone still connected)? I realize > it would take a long time for that to happen, but was curious. Digging > through the code I could not find any handling for that and as far as I can > tell, it just increments the ID for each new connection until an exception is > thrown (Gnoga.Server.Connection.Connection_Manager.Add_Connection). ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Gnoga-list mailing list Gnoga-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gnoga-list
