Hi @ll!
My tcl-script is working perfectly ..thanks for your help folks!
BUT the bot is just running it user after user.
Is it possible, that the bot is serving the results of the script to several user at the same time and not one by one?
Thx in advance!
This is the new home of the egghelp.org community forum.
All data has been migrated (including user logins/passwords) to a new phpBB version.
For more information, see this announcement post. Click the X in the top right-corner of this box to dismiss this message.
All data has been migrated (including user logins/passwords) to a new phpBB version.
For more information, see this announcement post. Click the X in the top right-corner of this box to dismiss this message.
User requests for a script are in a stack
User requests for a script are in a stack
it's not a bug - it's a feature!
The script connects to a php site, which returns couple of results from a mysql db. The bot shows those results then to the user, who started that query.
But the script is able to return a pretty long list and any other user requests are on hold, until the script is done with the current user.
It would be nice, when the bot is able to work with several user at the same time and not one by one.
I was already wondering why the bot takes so long to post any results. The help for this query is in a local file and it shouldn't take long to read the file and msg it to the user. But the bot takes about a second per line (way to long).
But the script is able to return a pretty long list and any other user requests are on hold, until the script is done with the current user.
It would be nice, when the bot is able to work with several user at the same time and not one by one.
I was already wondering why the bot takes so long to post any results. The help for this query is in a local file and it shouldn't take long to read the file and msg it to the user. But the bot takes about a second per line (way to long).
it's not a bug - it's a feature!
The reasons why information is spat out 1 line per second is to prevent it being flooded off.
If you have lots of information as you state, then thie queue feature is doing you a favour.
If you are getting large amounts of requests, IE, your getting 2 requests queued for every 1 fulfilled, then you need a second bot.
You would have to run some form of load balancing script, to state which bot should do the processing.
I did have some code that would perform load balancing, and it wouldn't take long to remake now that the theory and knowledge has been obtained.
If you have lots of information as you state, then thie queue feature is doing you a favour.
If you are getting large amounts of requests, IE, your getting 2 requests queued for every 1 fulfilled, then you need a second bot.
You would have to run some form of load balancing script, to state which bot should do the processing.
I did have some code that would perform load balancing, and it wouldn't take long to remake now that the theory and knowledge has been obtained.
Ok, that makes sense, that the bot doesn't want to be flooded off the server 
I already thought about it to make a script, which builds its own queue and notifies every user, that he is on hold (may be with the queue number). This way, the user doesn't make any more requests, because he thinks the bot died (this would build up the bot-queue pretty good).
Is it possible to hold the process of one script as soon as a new requests comes in, adds the new request to the queue and returns to the other script? Otherwise i need a 2nd bot to do this, because of the process queue of the bot.
I already thought about it to make a script, which builds its own queue and notifies every user, that he is on hold (may be with the queue number). This way, the user doesn't make any more requests, because he thinks the bot died (this would build up the bot-queue pretty good).
Is it possible to hold the process of one script as soon as a new requests comes in, adds the new request to the queue and returns to the other script? Otherwise i need a 2nd bot to do this, because of the process queue of the bot.
it's not a bug - it's a feature!