anchor.diff:  a. Event callback registration: Users can register three types of handles in the loop. 
   
   * RX handle: These handles are used for receiving packets. Currently only one RX handle is supported. This callback is called when any type of packet is received.
  -* TX handle: Multiple TX handles can be registered. Each handles callback will be called once per event loop iteration.
  -* Timer handle: This handles callback will be called after a fixed timeout.
  +* TX handle: Multiple TX handles can be registered. Each handle’s callback will be called once per event loop iteration.
  +* Timer handle: This handle’s callback will be called after a fixed timeout.
   
   b. With each instance of a handle, one callback function is registered. This is called when the event has occurred.
   
  
positive.code: * Assign user specified parameters to the physical device.
  In the Twister API, all the above initialization steps are formed by single API call which is: *tw_init_global(argc, argv)*
  
  The user specified parameters for the physical device are provided in the port_conf file. This file must be present in the application directory. The parameters are further explained in the below section:
  
  === Port Management 
  The port management is assigning specific parameters which include IP address, subnet mask, gateway IP to the port. All this is done in the initialization module. The user just hast to provide a file to the module, which is *port_conf*. The configuration file should be in JSON format and a sample is provided below:
  
negative.code: [width="15%"]
  |===============================================================================================================================
  |*Sr.* | *Twister* | *Libuv*
  |1.  | *tw_default_loop:* Reserve memory for an event loop with which handles can be registered. The loop’s total time to run is also provided | *uv_default_loop:* Reserve memory for an event loop with which handles can be registered
  |2.  | *tw_<handlename>_init:* Reserve memory for handle pointer and register it with an event loop instance | *uv_<handlename>_init:* Reserve memory for handle pointer and register it with an event loop instance
  |3.  | *tw_<handlename>_start:* Register a callback function for the handle| *uv_<handlename_start>:* Register a callback function for the handle
  |4.  | *tw_run:* Start the event loop | *uv_run:* Start the event loop
  