|
You are here |
linksort.com | ||
| | | | |
markphelps.me
|
|
| | | | | Mark Phelps' blog | |
| | | | |
www.joeshaw.org
|
|
| | | | | A scheme for consistent and safe HTTP API errors | |
| | | | |
blog.carlana.net
|
|
| | | | | The other day, I was reading a website about some historical documents, when I saw that it had an error message on top: Screenshot from the site Some quick searching online for the error message revealed that it was caused by a mismatch between the site's versions of PHP and WordPress. Older versions of WordPress had a bug in the switch statement of a certain localization component, and later versions of PHP dump a warning about this bug out to the end user HTML. When I came back to the site a few days later, it had been fixed. The ultimate reason for my seeing for the error message as a random reader is that PHP has too many ways to deal with errors: Builtin PHP functions, and therefore any PHP project, have a whole range of error handling mechanisms - erro... | |
| | | | |
keithbabinec.com
|
|
| | | Normally we use SDKs to interact with Azure. Things like the Azure .NET SDK, the Azure PowerShell module, orthe dozens of otherSDKs listed here can be used. These SDKs provide a lot of helpful utilities and validation, but ultimately they will hit the Azure REST API once they need to phone home. Azure's REST APIprovides... | ||