We have been uncertain about the RemoteFacet name for a while now, since it suggests that the data for these facets is coming from a remote address, like a network connection. This is not the case (at least not the intention). The goal of the so called RemoteFacets is to encapsulate data that is shared with the "backend" (the game engine). From a technical standpoint, in Gameface at least, the memory holding this data is literally shared memory between the C++ host and the JavaScript environment.
As such, SharedFacet is a far more accurate name than RemoteFacet. It is also more clear, since it implies that other facets are not shared with the game engine, which is exactly the point of the other (so-called "local") facets.
This PR introduces a complete rename from RemoteFacet to SharedFacet.
Pending
[x] Equivalent PR for documentation (will be linked in the comments)
We have been uncertain about the
RemoteFacet
name for a while now, since it suggests that the data for these facets is coming from a remote address, like a network connection. This is not the case (at least not the intention). The goal of the so calledRemoteFacet
s is to encapsulate data that is shared with the "backend" (the game engine). From a technical standpoint, in Gameface at least, the memory holding this data is literally shared memory between the C++ host and the JavaScript environment.As such,
SharedFacet
is a far more accurate name thanRemoteFacet
. It is also more clear, since it implies that other facets are not shared with the game engine, which is exactly the point of the other (so-called "local") facets.This PR introduces a complete rename from
RemoteFacet
toSharedFacet
.Pending