1. Alex Chee Daniel LaBare Mike Oster John Spann Bryan Unbangluang Collaborative Document Sharing In Conjunction With

2. 2 Scenario Alex and Bryan are working together to create a report and presentation. Alex needs to reference information within Bryan’s document, which is still in development. Problem: –How does Alex get the information he needs from Bryan’s recent changes?

3. 3 Current Solutions Distribute copies via E-mail, CD, USB Flash Drive, etc. Set up a LAN Set up a VPN for offsite access 3rd Party –FolderShare –TubesNow –BeInSync

4. 4 Problems They Face Conflicts –With multiple versions, which one is the most up-to-date? File Size Limitations Complex Setup and Interface Limited by Locality Centralized Sharing –Many issues, such as single point of failure

5. 5 Project Goals Conflict Prevention –Restrict modifications of a single file by multiple users No File or Total Shared Size Limit –The only limit is the size of the HD Ease of Use –Unobtrusive interface that blends seamlessly with Windows Explorer

6. 6 Project Goals Web Based –Work over any Internet Connection Decentralized Storage –No single point of failure –Files are as secure as the client machines –Minimize Server Bandwidth by deferring file distribution to Peers

7. How it Works 1 23 Computer 1 Creates a new Team Informs Server of the Team Computer 2 Joins the Team Receives Peer information Requests Files from Computer 1 Computer 3 Joins the Team Receives Peer information Requests Files from Computers 1 and 2

8. Our Solution Conflict Prevention –Utilize a Check-in/Check-out Model Ensures a file can only be modified by 1 computer at a time Check-in distributes latest revision to the team –Team and File based revision numbers Tracks changes and determines need to synchronize –Only a single Up-To-Date version across all team member computers

9. 9 Our Solution Peer-to-Peer File Distribution –Eases the bandwidth load off the central server Increases Scalability –Local Storage of files. No files stored on the central server As secure as the client machine No single point of failure –File synchronization is distributed amongst Peers Multiple locations to synchronize from

10. 10 Scenario Revisited How would Te@mSync solve Alex and Bryan’s problems?

11. Use Case Alex and Bryan are members of the same team Bryan checks in his latest changes to the Report Alex receives the changes and updates the presentation and checks them in Alex and Bryan’s boss requests to see the presentation while out of the office

12. Te@mSync Synchronize users local files –Seamless and effortless synchronization –No need for a repository server Check-in/Check-out model –Allows for offline editing –Prevents file conflicts Web access –Platform independent –Remote viewing/downloading

13. 13 Future Plans NAT and Firewall Traversal Native Mac and Linux Support Improve File Distribution Protocol –Bittorrent-esque Persistent Client-Server Connections –Remove 30-second Polling Web based Uploads ThinkFree Editing and More...

14. 14 What We Learned Programmed within many new frameworks and implemented multiple new APIs: –Ruby on Rails –Windows Platform SDK –Windows COM –ATL

15. 15 What We Learned Team Communication is Difficult –The Importance of WRITTEN Documentations and Specifications Resource Distribution and Time Management The Value of Version Control

16. Questions?

17. Network Overview 1 23