> I'm anxious to try this in ASSP. I've used Response Delays with other
software and 
> found it very effective. But I've used much longer delays (up to 40
seconds) and 
> I've also used delays after every command. One feature that I've found 
> works very well and helps to reduce the amount of time you are holding a
connection 
> open, is to check for additional commands coming from the sender BEFORE
you send 
> your response. If that behaviour is detected, you can be very sure that it
is a SPAMMER. 
> Then you can immediately take whatever steps you think are necessary.
> 
> Ken Eisman
> Information Services Director
> Matagorda County

100% correct. I know how effective this technique is, and I agree with you,
but fwik there are a few tech problems in doing this with perl. We already
discussed this feature a few months ago.

I hope fritz finds some way to implement this. He usually is very fast and
responsive to improvements great new features in assp. I suggested a few
hours ago to bypass nodelay.txt, ipwl.txt and ipnp.txt (and maybe more), and
.51 has a bypass for nodelay. 

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Assp-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/assp-user

Reply via email to