Update architecture.md
This commit is contained in:
parent
5b915daefe
commit
5ea3fe6dca
@ -61,12 +61,31 @@ But interface was still lagging behind the server. With XO 3.4, we got a full ev
|
||||
|
||||
### A proxy for your hosts
|
||||
|
||||
XO-Server will act as a proxy for all your clients. A good example is the console: you can now expose your consoles even if your clients are outside the network!
|
||||
XO-Server will act as a proxy for all your clients. It opens a lot of possibilities!
|
||||
|
||||
#### Console proxy
|
||||
|
||||
A good example is the console: you can now expose your consoles even if your clients are outside the network!
|
||||
|
||||

|
||||
|
||||

|
||||
|
||||
#### VM streaming
|
||||
|
||||
Another possibility is to stream a VM from a host to another.
|
||||
|
||||
To do that previously, you needed to export your VM somewhere, then re-import it:
|
||||
|
||||

|
||||
|
||||
Thanks to our architecture, it's now far better:
|
||||
|
||||

|
||||
|
||||
|
||||
#### Auto patching
|
||||
|
||||
### Pluggable
|
||||
|
||||
It's really easy to plug other modules to XO-server, and extend or adapt the solution to your needs (see XO-web and XO-cli for real examples).
|
||||
|
Loading…
Reference in New Issue
Block a user