Open AntonelloBS opened 2 years ago
LSL can communicate between processes on localhost, within a subnet, and even across the internet (the latter is maybe what you read w.r.t. configuration file changes). I'm not sure if this is what you meant by "web".
As for getting it in the browser -- whether that's on localhost or on another computer -- as far as I know there is currently no good way to pull
data from an LSL stream into a javascript process. websockets aren't implemented. So you would probably need a webserver that reads in data from LSL then serves it to browsers.
OK, can I force the inlet and outlet to communicate only on localhost? Do I have to use the knowPeers or the ResolveScope?
I've never used this feature so I don't know off-hand. I think KnownPeers is more of a fallback rather than a limiter. In addition to ResolveScope, you might want to look into LinkAddresses. Sorry I can't be more helpful at the moment.
What is link Adresses used for?
The most reliable way to understand what the different lsl_api.cfg entries do is to look at the code. In this case: https://github.com/sccn/liblsl/blob/master/src/api_config.h#L87-L103
Hello, for a project of mine I would like to send data acquired from a device with LSL to the Web. Right now I am pulling data from the device with a timeout of 0 and sending them to the web via HTTP post request (I am using HTTP connection pooling instead of classic HTTP). It is somehow a slow process, I can't get a good timing, so I have 2 questions:
Thanks