<div dir="ltr"><div><div><div><br></div><div>Hi John<br><br></div>You might check this out, it has information on what codes are used when. Not sure how closely the services hew to the spec, but...<br><a href="http://www.fdsn.org/webservices/FDSN-WS-Specifications-1.0.pdf">http://www.fdsn.org/webservices/FDSN-WS-Specifications-1.0.pdf</a><br>
<br></div>I don't actually know, but my guess is that too many requests in parallel would be silently killed by the load balancer/firewall thingy at the DMC as the request would never actually make it to the web service itself. Would be nice to have some official clarification so clients can avoid using too many threads/sockets.<br>
<br></div>Philip<br><br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Apr 15, 2013 at 6:01 PM, John D. West <span dir="ltr"><<a href="mailto:john.d.west@asu.edu" target="_blank">john.d.west@asu.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi.<div><br></div><div>I understand that the new FDSN web services return HTTP 204 to indicate no data returned, and applaud this move. </div>
<div><br></div><div>If the service is temporarily not available (say because I've made too many requests in parallel, system is busy, etc.) do I get a different return code? If so, what?</div>
<div><br></div><div>Thanks!</div><span class="HOEnZb"><font color="#888888"><div><br clear="all"><div> -- John</div>
</div></font></span></div>
<br>_______________________________________________<br>
webservices mailing list<br>
<a href="mailto:webservices@iris.washington.edu">webservices@iris.washington.edu</a><br>
<a href="http://www.iris.washington.edu/mailman/listinfo/webservices" target="_blank">http://www.iris.washington.edu/mailman/listinfo/webservices</a><br>
<br></blockquote></div><br></div>