Wednesday, November 30, 2005

Asynchronous Communication

There is a essential need for component(s) to support asynchonous behavior. Main points are:
  • Exchange of Request data and Response data between server and client. Particularly at the time of demise or disconnection of the receiving entity (in case of response from MH), assuming that sending operation is successful. Also in request scenarios where FH has pushed the request, but the request is travelling along the network but not reached to the server.

  • Exchange of control information between Routing layer. Exchange of Mobility layer connection information, handoff information.

  • Message broker can hence act as delegate, as indirectly it would be supporting disconnected operation.

  • TODOs:
  • Component identification and deployment diagram

  • Issues of hosting JMS and CNS on low footprint devices.

  • Many more...
  • No comments: