ReactOS Terminal Services
ReactOS Win32 personality a fully featured multi-user operating system with possibilities to log in several users at the same time with an insulated environment for every login. Every login should be able to access the terminal services from any interface with many different protocols enabling different possibilities depending on the protocol, interface, and connection speed.
- Multi-user environment.
- Possibility to log on remotely or locally via any interface (Serial, Parallel, USB, Firewire, Modem(Analog, Digital), Network).
- Possibility to log in several times from the same terminal + some type of fast switching like XP.
- Possibility to use two or more sets of keyboard, mouse and screen (Human Interface Device/HID) and associate a login to a certain set of HIDs.
- Possibility to split screen (Horizontal or Vertical) and use two sets of HID one associated to each split section (for computers connected to TV-set).
- Possibility to use RDP, Citrix, X-Windows client, Telnet or VNC as protocol/client.
- Possibility to give every login an insulated environment much like VMware.
- "Undo-Disks" -> ROS doesn't write do the real harddisk; Snapshot (in German this is called "Datenairbag")
- Possibility to let a session log in directly to an emulation environment like QEmu, MAME or VICE# to run other Operating System then the Terminal Server or software not compiled for the CPU.
- Easy management with the possibility to take over, see and redirect a session directly from the login screen.
Tasks need to be done
- Multi-User Environment
- Shared Session Memory Space
- SAS: make win32k notify Winlogon
- smss: move Kmode loading to csrss
- csrss: make it support multiple Win sessions
- logon/logoff procedures
- Win32k stuff (video / keyboard / mouse)
- One focus for every mouse & keyboard cursor
- Multi-Display Adapters and Display support
- Multiple Hardware Displays
- SplitScreen support for two sessions at the same Screen
- Multiple Virtual Display Drivers that can be associated to a login
- TSDDD Framebuffer Display Driver
- Creating support for different protocols and inserting the different project into ROS
- Telnet server daemon
- xrdp project - simple RDP server
Thoughts for hardware
- If system revolves around VNC
- Cheap dedicated hardware possible to build - a cost of £20 possibly for a dedicated kit-built VNC client
Thoughts about VNC
- Extend VNC protocol to allow access to local client's drives
- Extend VNC protocol for print files to be sent across in standard format (possibly Postscript?), then at client converted to printer-specific format, to allow printing to client's preferred local printer
- Possible addition of audio support to VNC?
- Possible extension to VNC to allow it to operate through Proxy servers with Java/executable clients
- ReactOS can detect "broken" sessions due to network disconnection, and retain session for the client to reconnect from another computer/when the network begins working again.
- VNC is built into display Kernel of React, so all video messages are captured and quickly and efficiently sent across the internet, reducing lag and server overhead.
The advantage of being with VNC over X11 based systems, clients are readily available (down to Java), saving on coding. The protocol is fairly efficient and fast, and allows clients to use ReactOS based servers without installing software locally - locally installed software may not be allowed by the client's computer administration policy.
- Optimizing Applications for Microsoft Windows 2000 Terminal Services and Windows NT Server 4.0, Terminal Server Edition
- Reverse-Engineering and Implementation of the RDP 5 Protocol by Erik Forsberg, Linköpings universitet
Microsoft RDP Specification
- [X.224]: Information technology - Open Systems Interconnection - Protocol for providing the connection-mode transport service
- [MS-RDPEXPS]: Remote Desktop Protocol: XML Paper Specification (XPS) Print Virtual Channel Extension