--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/content/Java/jetty-as-proxy.md	Sat Feb 15 16:19:17 2014 +0100
@@ -0,0 +1,14 @@
+Title: Proxying requests with Jetty
+Date: 2014-01-24
+Tags: Jetty
+Lang: en
+
+At work we develop a web based software for the automotive industry. On the server side we embed Jetty as HTTP server and Servlet engine. It's easy to configure in code and performs very well.
+
+Recently, we had to integrate a third party solution which comes as a virtual machine. This solution consists of some JavaScript APIs that need to talk to the VM. This setup gets you into problems with the [same origin policy](http://en.wikipedia.org/wiki/Same-origin_policy) quickly.
+
+For the deployment setup we mess around with [Apache](http://httpd.apache.org)'s [mod_proxy](http://httpd.apache.org/docs/2.2/mod/mod_proxy.html). This works but is not really manageable for our development machines.
+
+For development I wrote a couple of simple servlets that accept the request, use the JDK's [HttpURLConnection](http://docs.oracle.com/javase/7/docs/api/java/net/HttpURLConnection.html) to retrieve the content from the VM and pass the resuld back. While this works it was really ugly code.
+
+A bit of googling came up with Jetty's [ProxyServlet](http://www.eclipse.org/jetty/documentation/current/proxy-servlet.html) which looked promising. The real time saver was [Alan Hohn's blog post](http://blog.anvard.org/articles/2013/10/06/jetty-proxy-servlet.html) about how to use the proxy servlet. It allowed me to throw away all of our custom servlets and replace them with a single three-liner. Thanks, man!
\ No newline at end of file

--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/content/Smartphone/cyanogenmod.md	Sat Feb 15 16:19:17 2014 +0100
@@ -0,0 +1,13 @@
+Title: Cyanogenmod on my Samsung Galaxy S
+Date: 2012-12-28
+Lang: en
+
+I had previously [rooted](|filename|./odin-on-virtualbox.md) my Samsung Galaxy S to install a newer release of Android 2.3.
+
+While I was pretty satisfied with the device and the Android version it's running I'm concerned about the lack of security updates. By now it's clear that Android 2.x will not receive security updates any more.
+
+So I decided to give [Cyanogenmod](http://www.cyanogenmod.org) a try as they support the [Samsung Galaxy S](http://wiki.cyanogenmod.org/w/Install_CM_for_galaxysmtd).
+
+Since I already installed the clockworkmod recovery previously, flashing CM was as easy as downloading a zip file, booting into recovery and applying the update. The process took a bit of time but it went through smoothly. After a reboot I was greeded by a brand new install of CM.
+
+I was a bit concerned if the device is powerful enough to run a 4.1 version of Android. After all, the Galaxy S only has 384MB of RAM. So far it seems that my concerns were unfounded - CM runs quite smooth and the performance of the UI is acceptable.
\ No newline at end of file

--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/content/Smartphone/galaxy-s4-mini.md	Sat Feb 15 16:19:17 2014 +0100
@@ -0,0 +1,13 @@
+Title: My new handset: Samsung Galaxy S4 mini
+Date: 2013-12-26
+Lang: en
+
+My [trusty old Samsung Galaxy S](|filename|./cyanogenmod.md) running [Cyanogenmod](http://www.cyanogenmod.org) is beginning to show its age. The main shortcoming of the device is it's RAM - 384 MB is on the low side for running a current Android version.
+
+So I was looking for a modern device that would run Cyanogenmod. A Galaxy S4 would have been my first choice but I definitely don't like the form factor - it's a good deal larger than the old Galaxy S. The new device should really be about the same size as the old one. I ended up with a [Samsung Galaxy S4 Mini](http://www.samsung.com/uk/consumer/mobile-devices/smartphones/android/GT-I9195ZKABTU) which has similar specs to the "big" S4 but is the same size as the old Galaxy S. Oh, and of course [Cyanogenmod](http://wiki.cyanogenmod.org/w/Install_CM_for_serranoltexx) is supported, too :-)
+
+So I got the device fairly cheap by extending my existing mobile contract. Before I installed CM on the device, I only booted the stock firmware once to obtain IP address, IMEI etc. After that, I did the [rooting process as described on the CM device page](http://wiki.cyanogenmod.org/w/Install_CM_for_serranoltexx). Rooting went fairly smooth using the steps described there.
+
+I did a full backup of the old device using [Titanium Backup](https://play.google.com/store/apps/details?id=com.keramidas.TitaniumBackup&hl=en) and put the backup folder onto the removable SD card. After the SD card was moved to the S4 mini, I was able to restore almost everything.
+
+So far I'm pretty pleased with the experience: things run a lot smoother than on the old device (surprise, surprise). I have yet to find a good use case for the new gadgets like NFC.
\ No newline at end of file