FlyingHTTPServer coding rule

The following is the coding rule for the FlyingHTTPServer.

1. Formatting etc.

It is true that some part of source code readability should be dependent on just a matter of style i.e. whether the formatting
styles present in the source code is being coherent/unified. Mixing-up differnt formatting may make programmers feel some sort
of uncomfortable. So the following formatting rule is adopted.

<Line length>
Each line length has to be at most 128 characters long.

<Spaces vs Tab>
Use only spaces. Do not use Tab.

<Function declaration>
Please find the following sample code snippet.

- free function -
ReturnType doSomething(ArgType1 arg1, ArgType2 arg2);

- class member function -
ReturnType SomeClass::doSomething(ArgType1 arg1, ArgType2 arg2) const
{
}

- class declaration -

struct SomeClassImpl;

class SomeClass
{
public:
    ReturnType doSomething(ArgType1, arg1, ArgType2 arg2) const;

private:
    mt::AutoPtr<SomeClassImpl> impl_;
};

to be continued.

