Last night I spent a couple of hours trying to find a clean way to implement this loop:
http://code.google.com/apis/maps/articles/phpsqlgeocode.html#samplecode The main thing here is that each loop loop iteration is expensive, so whatever persistence mechanism is in place needs to happen right away, or at least frequently. The other thing is that Google gets to say slow down any time they want. They recommend that the writer add an artificial delay before each loop iteration, and to increase that delay by 0.1 second any time the 620 status shows up. (Also, if you get the slow down code, you need rerun that iteration.) Normally I just do a little combinator happiness and I'm done. Not so much here. Anyone care to weigh in on how you'd approach this? I tried putting together a loop utility where the delay was increased and iteration retried every time the iteration threw a particular exception. But I was like "try this" and factor was like "unbalanced branches" and then I was like "infer. doh! try this" and it was like "unbalanced branches over here now". I never did get it working. Plus, I was bothered by the nagging idea that there was probably an important utility somewhere I was missing. -- Darrin ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Factor-talk mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/factor-talk
