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...

What lies Next

I listed following points on 08 April, 2005,

Impromptu Service Discovery - UPnP, JINI, SLP protocols

Minimal CORBA - low footprint

Asynchronous Behaviour - asynchronous messaging of request-responses, cache, use of CNS

Network Adaptation - access to MAC layer, adaptation according to MAC layer

Disconnection Operation - object by value, externalization and life cycle services, Use of mac layer for switching modes

Optimizing IIOP layer communication - analysis of architecture

Integration with Non- CORBA clients- SOAP, web service clients and others

Security Aspects- Authentication and Authorization services, security services

Early thoughts on Mobile ad-hoc networks - using Peer-to-Peer Computing

In last 8 months I delved inside very few of above, but I am recharged now, I would move to following points (In priority):

Asynchronous Behaviour - asynchronous messaging of request-responses, cache, use of CNS

Minimal CORBA - low footprint

Disconnection Operation - object by value, externalization and life cycle services, Use of mac layer for switching modes

Network Adaptation - access to MAC layer, adaptation according to MAC layer

Integration with Non- CORBA clients- SOAP, web service clients and others

Optimizing IIOP layer communication - analysis of architecture

Security Aspects- Authentication and Authorization services, security services