Reserved Names
DJSeed has a handful of reserved event names and environment variables names that cannot be overridden or reused without potentially breaking functionality.
Environment Variables
These variables are utilized in the parent and worker threads to help communicate primitive information. Assigning or overriding these variables will most likely cause breakage if you don't know what you are doing.
DJSeed::Cluster_Util_EnabledDJSeed::Total_Shard_AmountDJSeed::First_Shard_IdentifierDJSeed::Last_Shard_IdentifierDJSeed::Child_Cluster_IdentifierDJSeed::Total_Child_Cluster_Amount
Cluster Util Events
These are events emitted on ClusterUtil and ClusterEventEmitter emitting these events manually with incorrect data may cause breakage.
Cluster_Util_InfoClusterUtilCluster_Util_ErrorClusterUtilCluster_ReadyBothCluster_DeathBothCluster_ErrorBothCluster_WarnBothShard_ReadyBothShard_ResumeBothShard_ReconnectingBothShard_DisconnectBothShard_ErrorBoth
Process IPC Payloads
Not to be confused with IPC... Process IPC is utilized to communicate primitave messages to the worker threads as it is the easiest way to communicate between processes. These are the most detrimental to the entire package so it is advised to stay away from using these names!
{
payload: 'event_name',
data: {
...
}
}
You can still use process IPC but it is suggested to structure your messages differently so you don't need to worry about conflicting payloads.
Reserved Payloads
Cluster_Shards_PreparedCluster_Stats_ResponseCluster_Stats_RequestBroadcast_Eval_ResponseBroadcast_Eval_RequestCluster_ErrorCluster_WarnShard_ReadyShard_ResumeShard_ReconnectingShard_DisconnectShard_ErrorCluster_ReadyDispose_Self_RequestDispose_SelfIPC_Broadcast_EventIPC_Send_To_EventUtil_All_Stats_RequestUtil_All_Stats_ResponseUtil_Stats_RequestUtil_Stats_ResponseUtil_Broadcast_Eval_RequestUtil_Broadcast_Eval_Response