I built a plain Java HTTP client on top of TCP sockets. Wait, I hear you say, that's nuts, why would anyone do that? Well, the homework assignment as a part of the recruitment process asked to create a HTTP client with configurable connection pooling in Java, and it turns out that Java Virtual Machine pools HTTP connections by itself, no configuration allowed. A pool on top of a pool wouldn't make very much sense, right?
So, naturally, I tasked myself with reimplementing the HTTP/1.1 myself, along with the connection pooling logic in barely 4 days. Luckily, I had previously written a networking library for my Android projects, so I had high-level API thought out, but the implementation underneath had to be written from scratch.
How did it end up? Well, for my future employer, good enough. For you? Take a look at my GitHub and you can let me know if you wish so.
So, naturally, I tasked myself with reimplementing the HTTP/1.1 myself, along with the connection pooling logic in barely 4 days. Luckily, I had previously written a networking library for my Android projects, so I had high-level API thought out, but the implementation underneath had to be written from scratch.
How did it end up? Well, for my future employer, good enough. For you? Take a look at my GitHub and you can let me know if you wish so.