 | ScoringProgramPipeClientSendPlayerData Method |
Sends PlayerData synchronously to the BCS queue.
Namespace: BridgeSystems.Bridgemate.DataConnector.ScoringProgramClientAssembly: BridgeSystems.Bridgemate.DataConnector.ScoringProgramClient (in BridgeSystems.Bridgemate.DataConnector.ScoringProgramClient.dll) Version: 1.0.923.1+8676f6447fd14feb672ed9c066f2812915b8f069
Syntaxpublic ScoringProgramResponse SendPlayerData(
string sessionGuid,
PlayerDataDTO[] playerData
)
Parameters
- sessionGuid String
- The guid of the session that player participates in.
- playerData PlayerDataDTO
- a DTO containing the player data:playernumber, first name, last name, country code
Return Value
ScoringProgramResponse
Remarks
Best practice is to send all player data with the
InitDTO. After the session starts
preferably the data is not changed to prevent unpredictable behaviour. By sending ParticipationDTOs, again preferable with the InitDTO,
you can specify which players start on which direction on which table.
If all players are known before the session starts only the corresponding player data of the participants of the session needs to be uploaded.
If players will make themselves known at session start-up by entering their playernumber on the Bridgemate then all
playernumbers that could be entered should be uploaded using a PlayerDataDTO.
See Also