So, a little late night googling and it turns out that there is somewhat of a schism in the web services world. Now, without too much history I am kindof a services nut! However, I do not know how I missed this fight on the WSDL, REST, WADL acronym soup debate. As it turns out often enterprise-y tools do an amazing job at creating compatible (and even usable) web services endpoints, often in the form of SOAP with WSDL's describing the endpoint. A little investigation here reveals though just how hard it is to integrate a REST-ful endpoint to these service (often the value add of the extensible schema and type definitions quickly negates the simplicity of the REST). IMO this really leaves people in two camps - those with the automated *tools* to read the service endpoints (and quickly gain traction on interacting with the objects) and the simplicity of the REST interfaces that have very little overhead since they exploit the existing underlying architecture. I am not going to go into a tizzy here on why this seems really stupid (note to self - I should really write up some thoughts on this...)... because through this research I have stumbled onto a nifty google project: REST API code-gen (in all its computer science-y acronym laden goodness) - this is really cool (short description here)!! 

sent via mobile

 Recently ran into an interesting problem - I wanted to move a content type (cck) that I had created from one feature to another (specifically to move it into a spaces enabled feature to gain some of those benefits - thanks devseed!); however, as you might be aware (if you are stumbling across this) features is pretty smart - often *too* smart. When removing the content type from one feature it will effectively remove the content type from your drupal install; whilst if you add the content type to another feature in parallel features will ingeniously mark the other feature you have as a dependency. What we are going to exploit: drupal features caches with a version control system (VCS - I prefer git) and drush:

"So much mandated technology...they [generally large companies] just take the [provider] with the most steaks and the most strippers; typically from companies who have expense accounts and sales people who can sell them very expensive application servers over six months." http://twit.tv/floss79

A while back (2006ish) I wrote a small game for a class (Java mobile) and was curious if it would run on my phone today - what do you know?! Woohoo - it works!

Just some old images I had laying around I wanted to get out there...

"...if Apple implemented a trial period it could really soften the blow (iPhone OS 4.0, perhaps?). The iPad could perfect the shareware model that almost has worked on the PC, and it wouldn't hurt to have trials on the iPhone either." Really?!?! Almost worked - I would argue total failure!