CODEWITHSUNDEEP
pythonhtmlautobahn
Benjamin Schroeder
Benjamin Schroeder

Reputation: 73

AutobahnPython Server HTML5 Front end

I have this AutobahnPython server up and running fine. https://github.com/tavendo/AutobahnPython/blob/master/examples/websocket/streaming/streaming_server.py

I want to attach a HTML5 Front end for capture of web cam video and audio. How do I get the HTML5 Blob to send through the socket I just created in HTML5 to the python socket server I also have running?

Is it sendMessage? https://autobahnpython.readthedocs.org/en/latest/websocketbase.html#autobahn.websocket.WebSocketProtocol.sendMessage

Upvotes: 0

Views: 327

Answers (1)

oberstet
oberstet

Reputation: 22051

Be prepared, doing what you want, and doing it right (which means flow-control), is an advanced topic. I try to give you a couple of hints. You might be also interested in reading this.

  1. WebSocketProtocol.sendMessage is part of the AutobahnPython API. To be precise, it is part of the message-based basic API. Whereas the streaming server above uses the advanced API for receiving, it uses the basic API for sending (since the sent data is small, and there is no need for flow control)

  2. Now, in your case, the web cam is the "mass data" producer. You will want to flow-control the sending from the JS to the server. Since if you just send out WebSocket messages from JS as fast as you get data from cam, your upstream connection might not keep up, and the browser's memory will just run away. Read about bufferedAmount which is part of the JS WebSocket API.

  3. If you just want to consume data is it flow into your server, above AutobahnPython streaming server example is a good starting point since: you can process WebSocket data as it comes in. Other WebSocket frameworks will first buffer up a complete message until they give the message to you.

  4. If you want to redistribute the data received by your server again to other connected client, you will want flow-control on the server's outgoing leg also. And then you will need the advanced API for sending also. See the reference or the streaming (producer) client examples - you can adjust the code to run inside your server.

Now if above all does not make sense to you .. it's a non-trivial thing. Try reading the first link to the Autobahn forum, and more about flow-control. It is also non-trivial since the JS WebSocket API has only limited machinery for doing this kind of flow-control, without falling back to invent your own scheme at app level. Well. Anyway, hope that helps a little.

Upvotes: 2

Related Questions