130 likes | 229 Vues
This project outlines the legacy system using Jabber-net chat client and the transition to a web service using SOAP and XMPP. Features include message exchange, buddy list management, and presence status. The MVC refactor enhances the architecture.
E N D
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 • Secure • Extensible
Legacy System • Jabber-net Chat client • Uses jabber-net XMPP library • Message with any XMPP compliant library • Google talk • Miranda • Apple ichat
Features • Connect • Presence status • Send/Receive messages • Buddy List • Add/remove buddy
MVC Refactor • Model: Wrap Jabber-net libraries • View: Model logic removed
THAT’S INSANITY! • Yes, we’re adding a step. But why?
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?
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