NetTalk Central

Author Topic: Net Simple server and qserverconnections  (Read 3283 times)

ramiro

  • Newbie
  • *
  • Posts: 47
    • View Profile
    • Email
Net Simple server and qserverconnections
« on: September 16, 2014, 12:24:26 PM »
Possible cause for which the entries in the queue (qserverconnections) are not deleted when the server closes the connection or when the client closes.
we are working with SSL and wholepacket.
Thank you all.

Bruce

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 11191
    • View Profile
Re: Net Simple server and qserverconnections
« Reply #1 on: September 17, 2014, 09:04:02 PM »
closing connections takes longer ("under the hood") than you might expect. The whole connection mechanism in TCP/IP is complicated. So a connection goes through a number of cleanup steps - you may need to wait 30 seconds, or more, before a connection actually disappears from the queue.

cheers
Bruce

ramiro

  • Newbie
  • *
  • Posts: 47
    • View Profile
    • Email
Re: Net Simple server and qserverconnections
« Reply #2 on: September 18, 2014, 10:39:02 AM »
Hi Bruce,
Thanks for the information, however I'm talking about connections that remain even hours in the queue, we have verified the situation and we have seen that are dropped connections due to problems with the internet.
Thank you very much.

Bruce

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 11191
    • View Profile
Re: Net Simple server and qserverconnections
« Reply #3 on: September 18, 2014, 07:55:06 PM »
ok, if a connection is not "closed" - but rather just "lost" then neither side is notified. In this case both sides can still "see" the connection - it'll only generate an error when you actually try and use it.

Bear in mind that connections are not "physical". They're just stuff in data at both ends. So when a "connection" is established, it's not like some physical line is drawn between two points. It's just an "agreement" of both sides to configure some internal data structures in a certain way. "Closing" a connection is one side telling the other that they're done, whereas "losing" a connection is some physical thing that happens between them, which neither can detect.

Some protocols institute timeouts, or "heart beats" to check if the connection is still valid.

cheers
Bruce