Drcom-Client Project Goals
Introduction
Drcom-Client is an open source ISP client for Dr.COM® networks, a specialized broadband access and authentication system produced by Doctorcom Corp. However, Dr.COM® has been used in many univerisites of China while its official client has only Windows version, which makes Linux/MacOSX users take much pains on internet access. Even with its official Windows client, users still have got dozens of problems, especially for its prevention of NAT/proxy servers.
Drcom-Client Team wish everyone could enjoy his freedom in internet access. That's the reason why we offer Drcom-Client's source code.
Goals
- ISP Client
- The project's primary focus is to make it as a general-purpose ISP client for Dr.COM® networks, especially for Linux/MacOSX users. With Drcom-Client they will not be worried about no client for internet access any more.
- Open Source
- Drcom-Client should remain freely usable for open source applications. To that end, we use the GPLv2 license.
- Security
- Protecting users from security violations is critical. We fix security issues promptly to protect users and maintain their trust.
- Stability
- We strive to focus on the stability of Drcom-Client. It means we would deal with crashes, hangs and regressions promptly, rather than letting them pile up.
- Compatibility
- We strive to maintain and improve Drcom-Client protocol compatibility with existing Dr.COM® networks.
- Performance
- Maintaining and improving speed and memory use is an important goal. We never consider performance "good enough", but strive to constantly improve.
- Usability
- To work in accordance with good human interface design principles, and to mesh well with platform-native HI conventions, we strive to provide more features for better user experience, including those with disabilities.
- Portability
- We want to make it reasonable to port Drcom-Client to a variety of desktop, mobile, embedded and other platforms. We will provide appropriate and providing friendly embedding APIs.
- Hackability
- We try to keep the code relatively easy to understand, even though the protocol may become more complex. We strive to write clear, maintainable code, and we continue to improve names and code structure to aid understanding.
