1 / 27

Microsoft .NET P2P

Team Members Ben Miller Kevin Moore Steven Rysavy . Faculty Advisor Prof. Manimaran Govindarasu. Microsoft .NET P2P. Dec01-09. May 1, 2002. Client Dan Fay. Presentation Outline. Definition of Terms Problem Statement Design Objectives End-Product Description

honey
Download Presentation

Microsoft .NET P2P

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Team Members Ben Miller Kevin Moore Steven Rysavy Faculty Advisor Prof. Manimaran Govindarasu Microsoft .NET P2P Dec01-09 May 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 ICQ MSN AOL

  6. Design ObjectiveFunctionality • Rich Text Messaging • Rich Text has colors, fonts, and sizes • File Transfer • Special Support for File Types • Local Message History • IP Caching

  7. Design ObjectiveConstraints • Functionality provided by .NET Framework • System Resources • Connection Resources • No central server

  8. Design ObjectivesUsers • .NET environment enthusiasts • People seeking a rich text messaging application

  9. 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 End-Product DescriptionFeatures

  10. End-Product DescriptionOwnership • Code will be sent to our sponsor at Microsoft • Full project will be submitted to .NET community sites: • www.gotdotnet.com • www.devhood.com • www.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. Benefits Wide scale deployment Well defined, simple interface Drawbacks Not at all P2P Implementation would be trivial MSN Integration

  16. 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 .NET P2P Framework

  17. 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 Roll our Own

  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

  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

More Related