shadowsocks-windows

History

Syrone Wong 46d95e7411 Get rid of lock(this) - 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>		8 years ago
..
Service	Get rid of lock(this)	8 years ago

Strategy	make hints more friendly.	9 years ago

System	Fix typo	9 years ago

FileManager.cs	Minor changes	9 years ago

I18N.cs	add Traditional Chinese (#698)	8 years ago

Logging.cs	Misc	9 years ago

ShadowsocksController.cs	Replace treewide polipo with privoxy	8 years ago

No Description

C# JavaScript Markdown Protocol Buffer

clowwindy42@gmail.com gang.zhuo@gmail.com withguohao@gmail.com wong.syrone@gmail.com clowwindy@users.noreply.github.com timemanager.rick@gmail.com licshee@yen.ai 1@kimwong.me kimw@users.noreply.github.com mmgac001@gmail.com one@kimwong.me wzxjohn@users.noreply.github.com lunt.luo@gmail.com oshirisu.red@gmail.com max.c.lv@gmail.com r18@ikk.me sinsinpub@gmail.com bu213200@gmail.com zhuyilun8@hotmail.com jenkins-ci-bot@users.noreply.github.com Noisyfox He mave@foxmail.com snovian@gmail.com bombless@126.com canbingzt@gmail.com