The BlocklyProp client currently provides an embedded web server that facilitates communication with the client browser to obtain binary images that it then loads onto a connected Propeller device. The current implementation does not support end to end secured communication when the web browser is using HTTPS to communicate with the BlocklyProp server.
@michel-cf has proposed to re-architect the solution to use WebSockets in this post. The proposal will require an additional service from the cloud infrastructure and a significant rewrite of the existing code base.
This ticket will track the overall progress of the effort.
Created a test bed using the Autobahn package to manage WebSockets within the client. This should eliminate the weird dependency tree on ws4py/wsgi/cherrypy that is currently in place.
The BlocklyProp client currently provides an embedded web server that facilitates communication with the client browser to obtain binary images that it then loads onto a connected Propeller device. The current implementation does not support end to end secured communication when the web browser is using HTTPS to communicate with the BlocklyProp server.
@michel-cf has proposed to re-architect the solution to use WebSockets in this post. The proposal will require an additional service from the cloud infrastructure and a significant rewrite of the existing code base.
This ticket will track the overall progress of the effort.