egghelp/eggheads community

flood check

2009-02-03T12:38:47-04:00

That performance-issue would be restricted to Tcl 8.0, and would still be flawed with the byte vs char issue...
In any case, I fail to see how that is related to the topic.

@tmyoungjr:
I believe user posted a very flexible throttling-mechanism that could easily be adopted to your script.
Check this post: http://forum.egghelp.org/viewtopic.php?p=75097#75097

arfer's approach is interresting, yet may cause the script to stop responding should any I/O-errors occur during the reading. Would probably be a good idea to move the utimer to the top of the proc.
Also worth mentioning, is that this will keep resetting the bind-counter every time it triggers.

A third option would be to simply use timestamps, removing the need for any timers or cleanup. Example posted below:

Code:

proc throttle {id time} { if {[info exists ::throttle($id)] && $::throttle($id) > [clock seconds]} {  return 0 } set ::throttle($id) [expr [clock seconds] + $time] return 1}proc myproc {} { if {[throttle "theid" 60]} {  #we're ok, do the good stuff here } {  #still throttle'd, do nothing  return 0 }}

Statistics: Posted by nml375 — Tue Feb 03, 2009 12:38 pm

flood check

2009-02-03T08:58:41-04:00

Performance

... there is one trick that might be necessary. Determine the size of the file first, then 'read' that many bytes. This allows the channel code to optimize buffer handling (preallocation in the correct size). I don't know anymore who posted this first. But you only need this for Tcl 8.0. This is something for the Tcl Performance page as well.

from How do I read and write files in Tcl

Statistics: Posted by TCL_no_TK — Tue Feb 03, 2009 8:58 am

flood check

2009-02-02T12:14:32-04:00

TCL_no_TK:
What would the purpose of such a modification be?

Also, the extended syntax of read specifies the number of characters to read, while file size returns the number of bytes. Which certain charsets, such as UTF-8, one character may consist of several bytes. You will get away with this, as read, for normal files, reads as much as "numChars" charaters, or up until EOF, which ever comes first. Should the channelId however have been a serial port, the read command would block until the specific amount of characters have been recieved (of course, file size would not be useful on a serial port in the first place).

The point being, there is no good reason for specifying the number of characters to read, should you desire to read the whole file.

Statistics: Posted by nml375 — Mon Feb 02, 2009 12:14 pm

flood check

2009-02-02T07:25:32-04:00

Code:

  set fl [open fact.txt]   set data [read $fl]

Replace with

Code:

  set fs [file size "fact.txt"]  set fl [open fact.txt]   set data [read $fl $fs]

Statistics: Posted by TCL_no_TK — Mon Feb 02, 2009 7:25 am

flood check

2009-01-30T21:23:09-04:00

I know you said the above worked but recent coding I have done on something unrelated has caused me to rethink the solution I provided, as a generic means of preventing flood. I found the solution below to be more reliable.

Code:

bind pub - !fact pub_fact proc pub_fact {n u h c t} {   unbind pub - !fact pub_fact  set fl [open fact.txt]   set data [read $fl]   close $fl   set lines [split $data \n]   set randline [lindex $lines [rand [llength $lines]]]   putserv "privmsg $c :$randline"   utimer 60 [list bind pub - !fact pub_fact]  return 0 }

Statistics: Posted by arfer — Fri Jan 30, 2009 9:23 pm

flood check

2009-01-28T17:28:08-04:00

thank you - this works wonderfully

Statistics: Posted by tmyoungjr — Wed Jan 28, 2009 5:28 pm

flood check

2009-01-07T14:53:15-04:00

bind pub - !fact pub_fact

proc pub_fact {n u h c t} {
global varTimer
if {![info exists varTimer]} {
set varTimer 1
utimer 60 [unset varTimer]
set fl [open fact.txt]
set data [read $fl]
close $fl
set lines [split $data \n]
set randline [lindex $lines [rand [llength $lines]]]
putserv "privmsg $c :$randline"
}
return 0
}

Statistics: Posted by arfer — Wed Jan 07, 2009 2:53 pm

flood check

2009-01-07T11:22:02-04:00

I have a real simple script that i found here in the forums :

Code:

bind pub - !fact pub_factproc pub_fact {n u h c t} {  set fl [open fact.txt]   set data [read $fl]  close $fl  set lines [split $data \n]  set randline [lindex $lines [rand [llength $lines]]]  putserv "privmsg $c $randline"}

i'll modify it a bit for my needs. what i'm looking for tho is flood control. i want to limit the # of times this script will return anything (something like say 1 request every minute or some such). i've found many scripts with flood control built in, but they all seem excessively complicated for my needs. any assistance would be great.

Statistics: Posted by tmyoungjr — Wed Jan 07, 2009 11:22 am