I've ever go ahead. This one then is clever online specific. Optimizing architects
and sitting for multi-tenant collaboration. Okay, so I just try and set the groundwork a little
bit first as to how things were before I went near it. So starting on the left, you've got
like a clever online server called WSD and on the right hand side we have two documents that
are open. So you can see the one kit broker and then there's another one kit broker. Each one of
them is a documents. We each document is opened up in a different process. So you have one
or a clever online server. We have two documents open, each document is open in the process.
And then in between we have this far case which purpose is just basically to generate the
kits that documents eventually open up in. So in between this far case, increase the things
that turn into documents. And you can see that as I've just tried documents in use and there's
one kit spare that's waiting for the next document to come along and each one of those is basically
a bar office. And that's one waiting two open open documents. One of the opens up a document that
would be a kit broker for the moment it's waiting for that to happen. So the far kits job is to make
kits that then are basically free office and the open up documents. And there are spares ready to
use. And this is all done for our performance reasons. The bucket does the initial initialization
opens. It's the start-up of free office. And once it's done, the slow start-up, you know
free office as well as the slow start-up. It does that slow start-up. And then because it
is start-up, the other ones are quick to generate. And then because we keep ones ready to use
already, it's even quicker again. So that's where they're starting from. Each one of the
documents that each case is run inside and it's on CH jail which so each one of those documents
is in its own separate little world. And what's notable is that the bucket that starts up,
it starts up in the ordinary environment. And then afterwards when it sparks the individual children
themselves are inside the jail. So the bucket itself is not in the jail because it was in the jail
then the other ones, you know, they're not ready to be in the jail and that's causing a problem.
So you start off not in the jail and then each document is open up in the jail. In the middle
where the document is inside and these things that's modified, we save the document out otherwise
it's been disaster. But everything else inside in the case is thrown away. So if you're inside
in a clever online, you right click in a misspelled world and you say you want to ignore it.
And then when you exit that session and you start a new session, that word will be
misspelled again because there is no storage between a version between
Kate and since it's except for the document itself. So that's your starting place. Everything is
thrown away and what we want to do is to do two things. One of which when we do make changes for
instance to your spending and you save the these words to be remembered for the future,
we want to place the store of us. We also want to bring in some of the things you have in the
yard nudist version. You have these user dictionaries I just mentioned known as the word books
which keep track of your misspellings. You also have auto text where you have these pre-canned
long sequences of text about a picker topic that when you trigger a particular keystroke,
they expand out these words. So classic ones are we are farm letters and you say the same thing
to multiple people or regular occasions. You just type in a little shortcut and you get out this
bioplytic text that matters and then we would also like to have those pro-organization
of pre-users. So if an organization can have like a stock text, stock auto text,
use a parallelization and individual users have their own individual or top of that and that's
obviously useful for spent checking as well. And we want all that to work and we want to be able to
keep this FarCate hierarchy stuff I showed earlier for the optimization is good. So again,
what we're looking at is single clabber online, maybe two different organizations, maybe a doctor's
one or maybe a research one, nothing to do with each other. They're all hosted by the same
you know, host organization that uses one clabber to mix cloud servers and then there's multiple
users in each one. Each organization who want to have different presets, a different set of initial
auto text, things and initial user dictionaries and each user then may want to have additional
ones on top of that. So you've got that hierarchy. So there's a way things change too. So the
original code of the SD, the original bucket is still there and at the very right inside you still
have each document in the case. What in between you have sub-focards and each one of those is
as the same shared configuration for the organization we're talking about. So the organization then
say it has an ex-doubt and hosts the very presets as one, they're as part of the configuration.
They're downloaders automatically for them and then they instantiate inside the sub-focards. So when
you have an individual document that's opened up from the user, the belongs to particular organization,
we have these ready and running already executing pre-populated with the organization's
auto text and the organization's spent check-in dictionaries and then the individual user ones are
installed on the fair right inside in the individual kits. So the user stuff ends up in the kits
in the right inside the organization of stuff ends up here in this new layer of sub-focards,
where everything is pre-populated. Sub-focards unlike a document when it disappears,
when we come to it and we hold onto them for a while in case you need to reopen a new document.
And then this is all configurable and then we cache everything again, configurably afterwards.
So that's, we have the dash at the end. In the most cases, the shared dash is not going to change
for our organization on a regular basis. So if an organization gives us, for our
the whole effect is that we start off with check-in file in for that, has information on
document, we extend it for this additional thing. We start downloading it as soon as
information is coming from. We're hopefully have all that downloaders or pre-cached and advanced,
but if not, when we eventually get to loading up the document, we download the document as always,
and we get to loading the document, we will delay the loading of that document until
and the sub-focards is available. And when the sub-card circuit is available,
it goes ahead and it launches the spare cases per usual, the spare kits available,
document opens and that. The idea of shared users is the same as what you have in
the labor office already, which is already the concept of shared directory, the user directory,
and also the concept of the process of a pre-set directory, which is when you're a first-start
copies, things come. For this all fits in with how labor office works already.
And to, we splice on our new paths for auto-text and user-dictionaries onto the existing
directories we have for that. And also, there's a lot of settings we haven't available.
Towards the browser settings and online, we can also put them in the same storage as we're putting
these auto-text into. And we already have the existing labor office xu file format for
configuration there. So this is also supported for changing settings as well. Just a one example
little kind of practical issue. I mentioned earlier about the forecast and how that starts off
a user environment and the new within the sub-environment is that in that sub-environment the paths
are different than the outside environment. This is not a problem normally until we start using this
and then we're looking for auto-text paths that actually try out to be inside the individual
document. You're still getting the same paths as they were outside in the original market.
And that's a problem because you can't find them. So there's a whole complicated process of where
you have to basically re-initialize things to get the bypass and then there's a kind of a chain of
three or four issues down along. You have to get one thing re-initialize to get another thing
of re-initialize so that when these dictionaries are in the right place, they can be found.
So there's a number of tedious states. But the outcome is that if you're in the version of
Clara Online, a working version of one of these WAPI servers that supports the feature,
then you can add to your individual user dictionary like that. You can exit your document.
The next time you'll provide any document, desettings have been stored and you'll see them again.
And then at the end of all this to be able to administer them inside and leave it off as
a surf you have an options page. The concept of that options page you'll find in the next
hour which document settings pages which has been extended to include settings that are now hosted
from Clara Online itself. So there's flexibility for the future. And I'll just show you what it looks like
at the moment is that you're inside in the settings of the server itself. And the section here
that says author takes to workbook there like that, they have been coming from
Clara Online itself and gives you opportunity to add additional author text.
I delete the existing ones more books and user dictionaries. That's the personal settings for
individual ones and an admin admin user also has very similar settings. It's actually the same
visually that you can use the override the organization ones. Thank you very much.
you