Hi,
Our Client side code always uses 'rebind' to bind its Name context on Name Service. Scenario of problem is this:-
- First time client binds, everything goes fine.
- Theres a particular parameter which uniquely identifies our client.
- If we start another instance of client with that same parameter, server shud identify this new client and should communicate with this rather than previous one as 'rebind' call is being used on client side.
- But that doesnt happen , server still associates the client NameContext with previous instance of client.
Is my understanding of 'rebind' call wrong?
We use Visibroker ORB.
Regds
Ayaan
Our Client side code always uses 'rebind' to bind its Name context on Name Service. Scenario of problem is this:-
- First time client binds, everything goes fine.
- Theres a particular parameter which uniquely identifies our client.
- If we start another instance of client with that same parameter, server shud identify this new client and should communicate with this rather than previous one as 'rebind' call is being used on client side.
- But that doesnt happen , server still associates the client NameContext with previous instance of client.
Is my understanding of 'rebind' call wrong?
We use Visibroker ORB.
Regds
Ayaan