User Tools

Site Tools


receive_message_call_path

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
receive_message_call_path [2015/02/06 21:22]
John Light
receive_message_call_path [2015/02/06 21:33] (current)
John Light
Line 1: Line 1:
 Here is the call flow of a received message through the (threaded) Iotivity stack (as of 2/5/15): Here is the call flow of a received message through the (threaded) Iotivity stack (as of 2/5/15):
  
-Threaded ethernet adapter:+Threaded ethernet adapter ​(client):
   - CAStart [Uni|Multi]castServer {caethernetserver.c} -- start the ball rolling   - CAStart [Uni|Multi]castServer {caethernetserver.c} -- start the ball rolling
   - [gThreadPool] {caethernetserver.c} -- 20 threads shared among all adapters   - [gThreadPool] {caethernetserver.c} -- 20 threads shared among all adapters
Line 13: Line 13:
   - [gReceiveThread] {camessagehandler.c}   - [gReceiveThread] {camessagehandler.c}
   - CAHandleRequestResponseCallbacks {camessagehandler.c}   - CAHandleRequestResponseCallbacks {camessagehandler.c}
-  - [*gRequestHandler+  - [*gResponseHandler{camessagehandler.c} 
-  - +  - HandleCAResponse {ocstack.c} 
 +  - getResponseCallback {InProcClientWrapper.cpp} 
 +  - [application callback function]
receive_message_call_path.txt · Last modified: 2015/02/06 21:33 by John Light