Seems to me that any query that takes into account those two variables is going to put unnecessary and significant load on the database for each and every incoming notice, for what is surely an edge case.
Perhaps simply the logic of if(thisnotice==user.lastnotice) would suffice? And/or perhaps you ought to implement that in smsToLaconica. ;) Cheers, Ciaran Jon Spriggs wrote: > So, currently when a message is queued for submission, I guess it effectively > is > added to a database table, that is then handled by the various queue > handlers. > If, when the queue handler picks up a new update from any of the inbound > queues, > it checks what the last update was from the named account submitting that > change, and if it's seen the same message > $config[flood_control][num_messages] > in $config[flood_control][time_limit] minutes, it silently (or, maybe, not-so > silently - returning an appropriate HTTP error code - perhaps 409) ditches > that > update. _______________________________________________ Laconica-dev mailing list [email protected] http://mail.laconi.ca/mailman/listinfo/laconica-dev
