sensible http post timeout values programmatically arising requests?


when programmatically arising http post requests, timeout values sensible?



in case, i'm looking set 'sensible' timeout values origination post requests php, however relates any language.



i need means emanate set requests, any user-specified url. i need slight requests controlling instead concurrently, i'd mention essential over ask deemed have timed out.



php's 60 seconds. seems an unnecessarily enlarged wait before last ask going completed.



as post requests should finish fast - there's information retrieved returned request.



we should means assume, most time, disaster emanate response ask within x seconds means horde puzzled emanate response within reasonable values x significantly reduction 60.



surely hosts magnitude take some-more 60 seconds respond rudimentary post request. even magnitude take some-more 10 seconds? 5 seconds?



what competence essential values x practice? justifications concomitant suggestions severely beneficial.



Comments

Popular posts from this blog

list macos calm editors formula editors

how i practical urls indicate .aspx pages asp.net deployed an iis? (preferably but iis)

jaxb - xjc - reworking generated typesafe enum category members