 | ScoringProgramHttpClientSendPlayerDataAsync Method |
Sends PlayerData 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 Task<ScoringProgramResponse> SendPlayerDataAsync(
string organizationId,
PlayerDataDTO[] playerData
)
Parameters
- organizationId String
- The organization that gives out the playernumbers
- playerData PlayerDataDTO
- a DTO containing the player data:playernumber, first name, last name, country code
Return Value
TaskScoringProgramResponse
Remarks
Best practice is to send all player data first, even before initializing the session. After the session starts
preferably the data is not changed to prevent unpredictable behaviour. By sending ParticipationDTOs you can specify
which players start on which direction on which table.
If all players are known before the session starts only the participants of the session need 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.
See Also