However I'm now in a situation where I might need to install PEAR packages with a connection that may or may not be working, and I'm not sure exactly which packages I might need, so I wanted to know whether I could use PEAR as my packaging tool even when I wasn't able to reach the usual channels. And guess what? I can! Continue reading
OAuth::getLastResponse()to my error logs (this is PHP code, and you need to call
OAuth::enableDebug()before you make the request to get this output) so I could see that I was getting the following back from Google:
SSL is required to perform this operation.
Closer inspection shows that for one of the google endpoints, I had a prefix of
http:// rather than
https://. Those single-character bug fixes that take hours to find are my favourite!
In the first part of this (probably) 3-part series, we'll begin with the basics. It might seem boring, but the most important thing to get right with REST is parsing all the various elements of the HTTP request and responding accordingly. I've put in code samples from from a small-scale toy project I created to make me think about the steps involved (should I put the code somewhere so you can see it? Let me know). Without further ado, let's dive in and begin by sending all requests through one bootstrap script: Continue reading
My interest was mostly because I'm working on a book chapter which includes some static analysis content, and there are a couple of these tools that I include in my own builds, but I don't do much with the output of them. However I didn't want to drop anything from the chapter if it was actually a valuable tool and I was just missing the point - pretty much all the tools got a good number of votes though, so I'll be covering all of the above. It does look as if phploc has less of a following, however it's one of my favourite tools so it gets a mention anyway!
Thanks to everyone who took the time to vote; I thought I'd share the results in case anyone was interested.