User Tools

Site Tools


receive_message_call_path

Here is the call flow of a received message through the (threaded) Iotivity stack (as of 2/5/15):

Threaded ethernet adapter (client):

  1. CAStart [Uni|Multi]castServer {caethernetserver.c} – start the ball rolling
  2. [gThreadPool] {caethernetserver.c} – 20 threads shared among all adapters
  3. CAReceiveHandler {caethernetserver.c} – recvfrom() reads bytes
  4. [*gPacketReceivedCallback] {caethernetserver.c}
  5. CAEthernetPacketReceivedCB {caethernetadapter.c}
  6. [*gNetworkPacketCallback] {caethernetadapter.c}
  7. CAReceivedPacketCallback {cainternetcontroller.c}
  8. [*gNetworkPacketReceivedCallback] {cainternetcontroller.c}
  9. CAReceivedPacketCallback {camessagehandler.c} – differentiates between request/response
  10. [gReceiveThread] {camessagehandler.c}
  11. CAHandleRequestResponseCallbacks {camessagehandler.c}
  12. [*gResponseHandler] {camessagehandler.c}
  13. HandleCAResponse {ocstack.c}
  14. getResponseCallback {InProcClientWrapper.cpp}
  15. [application callback function]
receive_message_call_path.txt · Last modified: 2015/02/06 21:33 by John Light