1 / 13

Team 6 Web Service Project

Team 6 Web Service Project. Aaron Munger and Devin McBride. Outline. Introduction Legacy System Design Features MVC refactor Target System. Introduction. SOAP – Service Oriented Architecture Protocol XMPP – eXtensible Messaging and Presence Protocol Open Standard Decentralized

chaim
Download Presentation

Team 6 Web Service Project

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 6 Web Service Project Aaron Munger and Devin McBride

  2. Outline • Introduction • Legacy System • Design • Features • MVC refactor • Target System

  3. Introduction • SOAP – Service Oriented Architecture Protocol • XMPP – eXtensible Messaging and Presence Protocol • Open • Standard • Decentralized • Secure • Extensible

  4. Legacy System • Jabber-net Chat client • Uses jabber-net XMPP library • Message with any XMPP compliant library • Google talk • Miranda • Apple ichat

  5. Legacy Design

  6. Features • Connect • Presence status • Send/Receive messages • Buddy List • Add/remove buddy

  7. Legacy System Sequence

  8. MVC Refactor • Model: Wrap Jabber-net libraries • View: Model logic removed

  9. Planned MVC Architecture

  10. Web Service System Sequence

  11. THAT’S INSANITY! • Yes, we’re adding a step. But why?

  12. The Business Case • Always one step ahead everyone else, Google implemented Google Talk as a web service. • Operating Systems are going to the cloud. • Jabber is an open protocol. • Why not enable ALL jabber services easy XMPP chat access?

  13. Web Service Conversion • Legacy has Client Server architecture • Wrap the jabber-net library into a new web service library • Web service will use jabber-net • Initial web service will be soap based • Contract can be modified for a RESTful

More Related