Django WebSockets & WebHooks

Transcript

1. WebSockets & WebHooks Django
2. / jpadilla1
3. WebSocket is a protocol providing full-duplex communications channels over a single TCP connection.!
5. WebSocket Apps • Social Feeds! • Multiplayer games! • Collaborative editing/coding! • Sports updates! • Multimedia chats! • Location-based apps! • Online education
6. The problem with Django WSGI! Web Server Gateway Interface! ! WSGI does not support WebSockets out of the box
7. Solution
8. Problem • Hard to maintain • Dependent on another infrastructure • Other solutions include using Twisted or Tornado
9. What other solutions are there? +
10. https://github.com/jrief/django-websocket-redis
11. uWSGI supports WebSockets out of the box. Use Redis as a Messaging Queue More info -> http://django-websocket- redis.readthedocs.org/en/latest/introduction.html
12. Advantages • It is simpler to implement • The asynchronous I/O loop handling websockets can run • inside Django with ./manage.py run server • as a stand alone HTTP Server, using uWSGI • using NGiNX as proxy in two decoupled loops, one for WSGI and one for websocket HTTP in front of two separate uWSGI workers. • The whole Django API is available in this loop.
13. Demo time!
14. https://github.com/Jpadilla1/chatrooms
16. A WebHook is a “user-defined HTTP callback”.
17. Without WebHooks
18. With WebHooks
19. Before & After WebHooks
20. Django WebHooks https://github.com/pydanny/dj-webhooks! ! Or! ! Make your own
21. def send_notification(sender, **kwargs): ! m = kwargs['instance'] ! data = { ! "sent_by": m.sent_by.email, ! "content": m.content, ! "created_at": m.created_at ! } ! response =\ ! requests.post( ! url=settings.WEBHOOK_URL, ! data=json.dumps(data, cls=MyEncoder), ! headers={'content-type': 'application/json'} ! ) ! ! ! ! post_save.connect(send_notification, sender=Message)
22. http://www.webhooks.org/ More on WebHooks
23. +
25. Demo time!
26. https://github.com/Jpadilla1/messages
27. What it does • Receives a message through the API in Django! • Does a POST to the given WEBHOOK_URL with the data! • Node receives the data! • Node sends it off through a WebSocket to the app
28. What do we get? A event driven, realtime application… With third party services
29. Thank you Questions?