On Jul 13, 1:50 am, JavaJive <[email protected]> wrote: > For the results below where I am trying to create a reliable > system of recovery if an error is caused ...
I agree this is the most important part of the system, to have assurance it's going to work in all conditions, and so far there's been OVER_QUERY_LIMIT and UNKNOWN_ERROR, which require different handling. I will try to replicate your results with the UNKNOWN_ERROR: >> A: A subsequent re-sending of the request is almost guaranteed to >> fail with the same error >> B: Request(s) that initially return UNKNOWN_ERROR later appear to >> return OK, but by then the record of which transmitter the results >> refer to have been lost when the request object destroyed itself after >> the initial error. -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
