02b45cc4

Guide
- Move sets
- Pose constraints
- The variation harness
- Getting content into a running game
- Components
- Entity queries
- Booleans and handoff
- The editing pipeline
- Element selection
- Face materials
- Foliage mode
- Icons
- The editor shell
- Editable meshes in a scene
- Editor modes
- Building to a number
- Scene menus
- The shape tool
- Snapping
- Sub-object picking
- Sculpt and paint mode
- Writing an editor plugin
- Block-out shapes
- Booting an application
- Character movement
- Editable meshes
- Growing a forest
- Foliage instances
- Grass
- Mesh booleans
- Mesh operations
- Mesh surfaces
- Networked players
- Players and possession
- Splines
- Terrain brushes
- The terrain heightfield
- Painting a terrain
- Sculpting a heightfield
- Saving and restoring a world
- Admission, health and the control plane
- Durable state and the ledger
- Placing players
- Placing realms
- Shards, keys and specs
- The cluster
- The service plane
- Transfer tickets
- Transferring players
- Upgrading a fleet
- Writing a realm
- Drawing foliage
- Drawing grass
- Impostors
- Culling and streaming instances
- Turning on dynamic global illumination
- Meshes and materials, type by type
- Drawing particles
- Lighting a scene in lux and lumens
- Making a room look different
- The post-processing node kinds
- Making everything cast a shadow
- Drawing a terrain
By kind
- Components39
- Systems48
- Controls165
- Shaders48
- Graph nodes64
- Importers22
- Annotations45
- Diagnostics8
- Log events64
All namespaces275
Releases1

IRealmProcessHost

interface

Live/Vixen.Live.Placement.Process/IRealmProcessHost.cs:73

csharp

public interface IRealmProcessHost

How a realm process is actually started.

Read the guide page for this →

Remarks

The seam, and the reason it exists is doc 27 § Testing: "Vixen.Live.Placement.Process is to this document what Vixen.Net.Transport.Local is to doc 16". A test that asserts a fleet converges after a randomised sequence of kills, restarts and partitions cannot afford to be starting real processes — it would take minutes, it would be flaky on a loaded CI machine, and killing a process at an exact moment is not something a test can ask for.

So the backend is written against this, the default implementation is SystemProcessHost, and a test supplies one that starts nothing. The production path and the tested path are the same code above this line, which is the property that makes the seam worth its two interfaces.

Methods (1)

IRealmProcessHandle Start(RealmProcessRequest request)
Starts one.

Used by (3)

FakeProcessHostVixen.Live.Placement.Process.Tests
ProcessPlacementVixen.Live.Placement.Process
SystemProcessHostVixen.Live.Placement.Process