Is there any document ,Class diagram or something other like this?

Dec 6, 2011 at 5:20 AM

I think it is quite necessary ..

Dec 6, 2011 at 7:39 AM
Edited Dec 7, 2011 at 2:47 AM

I think low coupling is necessary since we can hardly raise meeting or other way to fast communicate.

I suggest providing comments for each class/member/method and top of each cs file to illustrate the function or usage of the class/member/method or file for all public/protected element.

Every interface of your components is suggested to comment in detail.

If you hope others understand your design or your components are highly coupled with others' components, you can provide more design information in project BitTorrentSharp.Design in the solution.

I have added KRPC time-sequence diagram in that, since KRPC may used by others, I will provide more details such as class diagram, code sample.

Basicly, I wish every components are less coupling with others, and interfaces, usage should be commented in detail. You can use any approach to illustrate your mind.