1 / 12

Pub/sub-based Web Applications

Pub/sub-based Web Applications. Walter Wong HIIT & NomadicLab 01.03.2010. Agenda. Current data delivery in the Web Pub/sub-based content delivery Implementation Evaluation Conclusion. Client. HTTP 200 OK. HTTP 200 OK. HTTP Get. HTTP Get. Server. Pull-based model.

peter-perkins
Download Presentation

Pub/sub-based Web Applications

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. Pub/sub-based Web Applications • Walter Wong • HIIT & NomadicLab • 01.03.2010

  2. Agenda • Current data delivery in the Web • Pub/sub-based content delivery • Implementation • Evaluation • Conclusion

  3. Client HTTP 200 OK HTTP 200 OK HTTP Get HTTP Get Server Pull-based model + Servers don’t save state - Clients constantly poll for data - Entire page download - No real time delivery capabilities :

  4. Client update! XHR Get (long poll) XHR Get (long poll) HTTP 200 OK HTTP 200 OK HTTP Get Server Push-basedHTTP long-polling + Clients request and wait + Almost real-time delivery + Servers send just the updated data (AJAX) - Servers keep open TCP connections - Clients request again after data delivery :

  5. Pub/sub-based for Web content delivery • Objectives • Real-time data delivery capabilities in the Web • Lower network bandwidth consumption (simple delivery channel - no TCP) • Lower hardware requirements (no connection maintenance) • Lower energy consumption (portable devices)

  6. Subscriber Subscribe(data) Publish(data) Publish(data) Publish(data) Publisher Pub/sub Model + Servers don’t save state + Partial page download + Real time delivery Capabilities + Consumes less energy

  7. Pub/sub-based for Web content delivery

  8. PSIRP Firefox plug-in

  9. Evaluation network

  10. PSIRP Firefox plug-in vs. HTTP long-polling

  11. Conclusion • Pull and push-based systems hinder real-time content delivery in the Web • Waste of resources mainly due to the host-centric client/server model • Publish/subscribe provides real-time content delivery with lower overhead • Implementation shows that pub/sub is simpler, requires lower hardware requirements and reduces the overall network traffic

  12. Questions? • Comments? • Thanks!

More Related