Solved! Go to Solution.
Our motivation for not documenting the comunication layerout is not about obfuscation, but hiding complexity and maintaining compatibility.
Anyhow, a few words about how the data layer communication works:
As I understand you want to have a portable python application between linux and windows. The Data Layer library is available for linux and windows. So perhaps we can find a convinient way to use these library in the different OS. Please can you elaborate what is the problem with python and datalayer SDK in windows, so that we can help you better?
"There is no chance that we will make the protocol public."
Why not? Wouldn't it be nice to have more people working on client libs for the Data Layer? I found this post when I was looking for the same information as Loïc because the python SDK keeps crashing and I would like to fix that..
currently I am experiencing issues when having a provider and a client in the same process. This is needed e.g. for automated testing: I want to check if my application is providing data to the data layer correctly. With the provider running, the data layer client receives a time out. Even if I start the client in another process (multiprocessing.Process) I run into connection errors.
Other issues are my provider crashing with a segfault after 30 seconds of providing data.
If you like I can try to produce some minimal code examples..