<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Http on Random Ramblings</title><link>https://blog.foundev.pro/tags/http.html</link><description>Recent content in Http on Random Ramblings</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 27 May 2020 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.foundev.pro/tags/http/index.xml" rel="self" type="application/rss+xml"/><item><title>Picking a web microframework for an existing Scala codebase</title><link>https://blog.foundev.pro/2020/05/27/picking-a-microframework.html</link><pubDate>Wed, 27 May 2020 00:00:00 +0000</pubDate><guid>https://blog.foundev.pro/2020/05/27/picking-a-microframework.html</guid><description>&lt;h1&gt;Picking a web microframework for an existing Scala codebase&lt;/h1&gt;&#10;&lt;p&gt;I&amp;rsquo;ve had to use this at work the last couple of weeks. We had a &amp;ldquo;home grown&amp;rdquo; framework for a new application&#10;we&amp;rsquo;re working and the first thing I did was try and rip that out (new project so didn&amp;rsquo;t have URL and parameter sanitization&#10;anyway to do routes, etc).&lt;/p&gt;&#10;&lt;p&gt;However, being that the group I was working had bad expierences in the past with frameworks, I had to settle on something that was light weight, integrated&#10;with jetty and allowed us to work the way that was comfortable for us as team (also it had to work with Scala).&lt;/p&gt;</description></item></channel></rss>