Chapter 1

Once connected, the sockets interface makes sending the packet straightforward and we
can simply call RSocket::Write().
void CGdpBTSender::TWriteState::EnterL()
{
// Initiate a write...
iSender.iWriteSocket.Write(iSender.iPacket, iSender.iStatus);
// and wait...
iSender.SetActive();
}
If the write is successful, we can let the handler know. We have also finished the send
operation, have no further states to go onto, and can return NULL.
CGdpStateMachine::TState* CGdpBTSender::TWriteState::CompleteL()
{
// Hey! We're done! Stop going through the state machine
iSender.iHandler->SendComplete(KErrNone);
return NULL;
}
Receiver
Receiving a GDP packet over Bluetooth differs very little from how you would receive data
from any other socket. We must listen for a connection, accept the connection, and then
read our data from the socket.
Figure 20.11 shows, two sequential operations are required to receive GDP packets via
Bluetooth:
Figure 20.11
� Accept: the incoming connection from sender.
� Read: read the packet from the connected device and while we have an active
connection we can wait for additional packets.
Before a connection can be accepted, we must give some consideration to device security.
From the earliest Bluetooth specification, device security has always featured heavily.
Typically connections cannot be made between devices without the consent of the user. For
this reason, we will need to create a session with the Bluetooth security manager (RBtMan)
to modify security settings for incoming GDP connections, to remove the requirement for