On 11/5/07, Jochem Maas <jochem@xxxxxxxxxxxxx> wrote: > > Nathan Nobbe wrote: > > On 11/5/07, Jon Westcot <jon@xxxxxxxxxxx> wrote: > >> Hi Nathan: > >> > >> No, I'm not familiar with Ajax. Where can I read up on it? More > >> important, how can I find out if Ajax is implemented on the server? Or > is > >> it something I can add myself? > >> > > > > although it might sound cool - using ajax to issue multiple requests is > NOT the > correct solution. correct implies there is only a single solution to the problem. i certainly did not suggest it because it *sounds* cool. the reason i suggested it, is because it is the best solution to receive feedback on the user interface while the queries are run. your merely moving the goalposts (what happens when user moves off the > page just as the third ajax request is made?) well, if you wanted to support that scenario, a resume feature would be pretty easy to implement. your looking to run a series of inserts whilst garanteeing that they are not > interrupted. i dont recall seeing that requirement. Dan Brown (the nice guy on this list, not the twat that wrote the 'daVinci > Code') suggests > a *much* better way to go- namely using a CLI script. an *alternative* solution, with the trade-off that notification via the u.i. is not an option. the fun part is getting a button > push on an admin page to somehow initiate the CLI script. that is nice. its also nice that the solution i suggested provides the same sort of button and updated feedback on the u.i. using a cli script is a great solution, however the only sort of notification mechanism is one that is sent after the queries have finished, via an email most likely. yes, there are many ways to skin the cat; evaluate them based on the requirements and the constraints and choose the best one for the problem. -nathan