Example - Send TD Message

The DLL has a built in Turbo Dispatch parser, that will convert the messages into Protocol Buffers (and back again on receive).  This enables you to support existing applications without too much effort.

static void SendTDJob ()
{
    //Job in Turbo Dispatch Format
    String NewTDJob = "\"9100,TEST-JOB\"\"1205,VEHICLE OVERHEATING\"\"1207,TOW TO CUSTOMERS HOME\"\"1004,900001\"\"1100,GH3987432 AC\"\"1101,VLADIMIR PENIAKOFF\"\"1102,FLAT4 34 EUSTON RD, LONDON N1\"\"1202,IN PETROL FLAP\"\"1103,FORD KA\"\"1105,EN52GTT\"\"1107,AUTO\"\"1108,1.6L\"\"1110,RED\"\"1200,EUSTON RD NEAR KINGS CROSS ST\"\"1201,01489 571500\"\"1210,DRIVER HAS DISABILITY\"\"1212,2nd CALL - PREVIOUS AGENT COULD'NT FIND\"\"1208,RECOVER TO SOUTHFIELDS\"";

    //Send via the Turbo Dispatch compatibility layer
    turboExchange.TurboDispatch.clsTDConverter.SendTurboDispatchMessage(Program.turboClient,NewTDJob);
   
}

Notes:

The destination TurboID number can be either attached to the top of the message (DEST=xxxxxxx\r\n), or specified on the
SendTurboDispatchMessage method.

There is no 512 character limit.  Just send everything in one message.

The parser has been tested with a verity of messages from different applications & sources.  Due to the nature of the Turbo Dispatch protocol, there is more than one way of doing things, and so if the parser fails, send an example message to support@turboexchange.net, and if necessary a new DLL will be supplied.

There is a fallback system in place, where if the parser gives up, it will pass the message on as a MessageWrapper.MessageType.turboTurboData message type, and let the recipient application try to parse it.  If you send your messages to the TestSuite, you will be able to see if this is happening (your message wont be broken down into fields).  Nothing wrong with this, except future applications without their own parsers will suffer (and we are trying to remove the need for complicated TD parsers for the future).