Using interfaces for Request and Response.

Begin reimplementation for Soup.

This is necessary since FastCGI implementation will not use libsoup
Message and MessageHeaders.
View can be streamed in the MessageBody.

This allow us to serve content that does not fit in the memory.

Ctpl uses OutputStream so that we can serve a very big template.
Compiling implementation for Soup.

Needs some refactoring and code cleanup, but the logic is good.

Using DataInputStream and DataOutputStream for body of Request and
Response as it is buffered and convenient for reading and writting
strings.
Working implementation for libsoup.

Request and Response are implemented using abstract class as they can
provide a part of the implementation.

This provides is a good basis to build FastCGI.
Abstract SGI to make application independant from their running servers.

Created SGI.Application to provide a request_handler and environment
variables.

Moved Request and Response abstract classes to SGI.

Use of Map type instead of HashMap.

Adds an example of headers handling with the new abstraction.
Adds query Map in Request to provide HTTP query.

libsoup Server provides a HashTable, so we just dump it into a Gee HashMap.