Signed-off-by: Syrone Wong <wong.syrone@gmail.com>

- naming private vars
- object initializer

Signed-off-by: Syrone Wong <wong.syrone@gmail.com>

And farewell.

This reverts commit be3cc3f3a6.

This reverts commit 0d4d01af3b.

This reverts commit 5ba0dffa5d.

This reverts commit f9e39fdd1d.

This reverts commit d1e8f38767.

This reverts commit f2b8e91f81.

This reverts commit b04c59d8e6.

This reverts commit 9cdb71875a.

This reverts commit 566a0fcfa5.

Check null ref (#940)

This coudl fix #937

No more http->socks5 transform.

Remove some debug output

Let TCP stack find a free port for us

Signed-off-by: Syrone Wong <wong.syrone@gmail.com>

This gives us the possibility to chose SS server based on dest address.

Signed-off-by: Syrone Wong <wong.syrone@gmail.com>

Signed-off-by: Syrone Wong <wong.syrone@gmail.com>

Also, fix typo in ProxyForm

Signed-off-by: Syrone Wong <wong.syrone@gmail.com>

Signed-off-by: Syrone Wong <wong.syrone@gmail.com>

Shadowsocks don't need to reconnect, which is the software's
responsibility to retry.

Signed-off-by: Syrone Wong <wong.syrone@gmail.com>

- Use readonly object as lock

Info from stackoverflow:

If I want to be sure that it will be locked for all threads inside my
application:
The lock object has to be static, if it locks access to static state.
Otherwise it has to be instance, because there's no need to lock state of
one class instance, and prevent other threads to work with another class
instance at the same time.

everyone says that the object has to be "readonly" I didn't found the
reason
Well, it doesn't have to be. This is just a best practice, which helps you
to avoid errors.

Signed-off-by: Syrone Wong <wong.syrone@gmail.com>

It is better to log them.

Signed-off-by: Syrone Wong <wong.syrone@gmail.com>

Signed-off-by: Syrone Wong <wong.syrone@gmail.com>

Signed-off-by: Syrone Wong <wong.syrone@gmail.com>