1. Microsoft.NET P2P Team Members Ben Miller Kevin Moore Steven Rysavy Faculty Advisor Prof. Manimaran Govindarasu Dec01-09May 1, 2002 Client Dan Fay

2. Presentation Outline Definition of Terms Problem Statement Design Objectives End-Product Description Assumptions and Limitations Project Risks and Concerns Technical Approach Milestones Future Work Human and Financial Budgets Lessons Learned Conclusion

3. Definition of Terms.NET Framework –Environment for developing software C# (pronounced “C Sharp”) –Object oriented language derived from C and C++ Peer-to-Peer Application –Internet applications with no central servers

4. Problem Statement Develop a peer-to-peer application using.NET framework Communicate using server-less environment Exchange multiple types of data Write in the C# language Document source code for developers

5. Examples ICQMSN AOL

6. Design Objective Functionality Rich Text Messaging –Rich Text has colors, f o n t s, and s i z e s File Transfer Special Support for File Types Local Message History IP Caching

7. Design Objective Constraints Functionality provided by.NET Framework System Resources Connection Resources No central server

8. Design Objectives Users.NET environment enthusiasts People seeking a rich text messaging application

9. End-Product Description Features Documented Code Connect using TCP/IP One-to-Many Connections Pure P2P Functional GUI Rich text (multiple fonts, colors, sizes, etc) Support for special types (emoticons) Message History (stored locally) IP Caching

10. End-Product Description Ownership Code will be sent to our sponsor at Microsoft Full project will be submitted to.NET community sites: –www.gotdotnet.comwww.gotdotnet.com –www.devhood.comwww.devhood.com –www.c-sharpcorner.comwww.c-sharpcorner.com

11. Assumptions The user is running an operating system that supports the.NET Framework Functionality of.NET will not vary among platforms The users are on an TCP/IP network Users will know the IP address of other clients.

12. Limitations Assuring unique identity and finding users might not be possible within a purely peer- to-peer environment. Firewalls may limit or deny communication between clients. Functionality will be limited by the capacity and availability of the network.

13. Project Risks and Concerns The.NET Platform may change between beta and final release.NET/C# are new technologies –Group members have to learn new a new language, framework, and tools –There is less information about.NET/C# than other, more established technologies

14. Technical Approach MSN Integration.NET P2P Framework Roll our own

15. MSN Integration Benefits Wide scale deployment Well defined, simple interface Drawbacks Not at all P2P Implementation would be trivial

16. .NET P2P Framework Benefits Designed with/for the.NET Framework Purely P2P in nature Provides functionality we couldn’t create in a semester Drawbacks Implementation would be trivial Only available in beta release Not stable

17. Roll our Own Benefits Fine control over features Demonstrates lower level programming Pride of building it ourselves Drawbacks Implementation is not trivial Limits our features No firewall support

18. Milestones M1 - Basic Functionality M2 - Additional Chat Features M3 – Special Features

19. M1 – Basic Functionality Connect to multiple clients Send simple text messages Functional Interface Projected Date: 4/27/01 Revised Date: 2/28/02

20. M2 – Additional Chat Features Sending of rich text messages Send files (push model) – Local end initiates the transfer Sharing files (pull model) – Remote end initiates the transfer Projected Date: 3/30/02 Finished Date: 3/30/02

21. M3 – Special Features Interoperability with other messaging applications and services Friendly names Emoticons Firewall connectivity Projected Date: 4/30/02 Finished: 4/30/02

22. Milestone Progress M1 - 2/28/02 M2 - 3/30/02 M3 - 4/30/02

23. Future Work Long term –Additional features Voice chat Whiteboard File Transfer

24. Human Budget

25. Financial Budget ItemEstimated Cost Actual Cost Poster$50.NET SDKProvided Visual Studio.NET Provided DocumentationProvided

26. Lessons Learned Testing should be ongoing part of development process Research features thoroughly before committing Managing development

27. Conclusion Goal –Build a peer-to-peer application that leverages the.NET framework Solution –Designed a peer-to-peer chat client using C# which is well documented and easy to expand