b59d160a08
The app is unimaginatively called "Mobile" for now. Runs but crashes pretty quickly after loading the document by the LO core. Will need some heavy changes to get a ClientSession object created in there, too, to handle the (emulated) WebSocket messages from the JavaScript. It would then handle some of these messages itself, and forwards some to the ChildSession, which in this case is in the same process. Now the messsages from the JavaScript go to a ChildSession, which is wrong. As the assertion says, "Tile traffic should go through the DocumentBroker-LoKit WS" |
||
|---|---|---|
| .. | ||
| Common.hpp | ||
| Crypto.cpp | ||
| Crypto.hpp | ||
| FileUtil.cpp | ||
| FileUtil.hpp | ||
| IoUtil.cpp | ||
| IoUtil.hpp | ||
| JsonUtil.hpp | ||
| Log.cpp | ||
| Log.hpp | ||
| LOOLWebSocket.hpp | ||
| Message.hpp | ||
| MessageQueue.cpp | ||
| MessageQueue.hpp | ||
| Png.hpp | ||
| Protocol.cpp | ||
| Protocol.hpp | ||
| Rectangle.hpp | ||
| Seccomp.cpp | ||
| Seccomp.hpp | ||
| security.h | ||
| Session.cpp | ||
| Session.hpp | ||
| SigUtil.cpp | ||
| SigUtil.hpp | ||
| SpookyV2.cpp | ||
| SpookyV2.h | ||
| Unit.cpp | ||
| Unit.hpp | ||
| UnitHTTP.hpp | ||
| Util.cpp | ||
| Util.hpp | ||