The executables are taking the user's input and going to the database to grab and cut out the pictures that are corresponding to the user's search term. I understand the stop button may solve some problems and I am going to test this some more. But there is still the need to stop a user from making some huge request then going away for a couple of days. I don't want to restrict the requests of a user however how can I stop them from monopolizing the server? thanks! "Chris W. Parker" <cparker@xxxxxxxxxxxx> wrote: newbie c on Tuesday, April 05, 2005 11:03 AM said: > Are these ideas practical and possible? Practically speaking? It seems like a waste of time. What are these executables doing? The stop button on the browser or clicking a link to a new page should suffice. As for possibility, that I don't know. I don't think you'll find the answer you want since HTTP is stateless. It seems that you'd have to send another request to the server to tell it to interrupt the current process. Your cancel "button" should probably just go to the new search page. Won't it cancel the process on it's own by abandoning the request? Chris. --------------------------------- Post your free ad now! Yahoo! Canada Personals
