 I'm Andrash Timar, Product Development Manager at Colabora Productivity, and we all have seen the excellent demonstration of Michael Meeks, so he demonstrated the Colabora Online and NextCloud interaction, but I'd like to say something about what's under the hood. So, you know, the Colabora Online is not a standalone product, so we didn't implement storage, didn't implement authentication, because we are doing what we are best at, so developing LibreOffice, obviously, and the online parts. So here comes NextCloud into the picture, so it has the storage, it has a user authentication, and we would like to put this together. We have been thinking about a protocol which can be used for communication between the storage and the Colabora Online, and fortunately, we found one. It's already an open standard, so-called, it's called VOPI, it's a web application open platform interface. So we just implemented part of this protocol, and it's basically an application for the NextCloud. The source code is on GitHub, so we are accepting full requests, and it consists of two parts. So the PHP part implements some rest endpoints that allow the transfer of the data, and there is a JavaScript part which loads the document into an iframe and starts to communicate to Colabora Online through a web socket. So basically, there are three rest endpoints that we need here. One is to get the document from the storage to the Colabora Online server. The second is to upload it back when we save. And the third is mandated by this VOPI protocol is to check file info, which can be used to transfer the file name, the user name, the file size, and the file version, so we can even do the versioning. So the authentication is done by a security token, which we generate on the NextCloud side. It is passed to the LibreOffice or Colabora Online server, and Colabora Online server downloads the document using this security token, which is validated at the NextCloud server side, so it's tied to a specific user session, and it can expire and has everything that it's required for proper authentication and authorization. The first step of the loading of a document is the calling of the so-called discovery service. This is also part of the VOPI protocol. This discovery service tells the VOPI host, NextCloud in this case, so what type of services can the VOPI client, the Colabora Online, can provide. For example, what document types are supported, or what document types are supported for viewing or editing. It's also possible to have different servers for different document types. In our case, everything is the same, so it's not over complicated. Then we serve our JavaScript from the Colabora Online side. We will reload it to an iFrame within the NextCloud, and then post the access token back to the server, and then we start to get ties over the WebSocket. So briefly, this is the architecture behind the Colabora Online and NextCloud application. The source code is on GitHub, and I'd like to invite you to our workshop after lunch, so we can discuss it in more details, and you can get involved. Thank you.