How is sessionId different from a JMS clientId in iBus//Mobile?
Both the JMS clientId and the iBus//Mobile sessionId are identifiers that should be set uniquely by the application developer. ClientId is the “usual” JMS clientId used for setting up the JMS Connections. SessionId is an identifier for each logical session that is established between the mobile device and the iBus//Mobile Gateway. Thus the sessionId uniquely identifies a session, i.e. : (i) For the simple case, when you have just one application running on your device, the sessionId is a unique identifier for the device itself. (ii) However, if you have multiple applications running on the same device, then each of these applications will need to have a unique sessionId. Thus, if applications A1 and A2 are running simultaneously on a mobile device whose IP number is a.b.c.d, then each application should set a unique sessionId, e.g. “a.b.c.d.A1” and “a.b.c.d.A2”. Although technically we could have reused the clientId for session management as well, we did not want to force the usage of
