Dave Page wrote:





-----Original Message-----
From: Andreas Pflug [mailto:[EMAIL PROTECTED] Sent: 17 February 2004 17:42
To: Markus Wollny
Cc: Josh Endries; [EMAIL PROTECTED]
Subject: Re: [pgadmin-support] connection dropping continued




I wouldn't call that malfunctioning,


So call it ill-configured.



I would call it malfunctioning, it's deliberately breaking tcp/ip by the sounds of it. You say it's to prevent DOS attacks, but isn't that exactly what it's caused itself?



, a simple "select 1;" issued every 30 odd
seconds to all opened databases would be absolutely


sufficient, I should


think. If that feature is off by default and can be switched on (and
maybe the interval adjusted according to needs), no one would be
bothered by it either.



I experimented with this following the last round of borked firewalls
and it's virtually impossible to do without screwing up pgAdmin
completely - there are all sorts of threading/concurrency problems that
would take a massive rewrite to sort out - something I'm not prepared to
do to work around a problem caused by a firewall that doesn't implement
TCP/IP properly.



Actually, it can be considered a BUG in the firewall, if it disconnects a tcpip session without sending the proper disconnect packet to the server, which assumes the connection being still valid and sitting on that open socket. Even web servers, routinely equipped with timeout functions themselves, would be delighted to be noticed about disconnects ASAP, to clean up services and save resources.


Regards,
Andreas



---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
     subscribe-nomail command to [EMAIL PROTECTED] so that your
     message can get through to the mailing list cleanly

Reply via email to