Unique key for Client/Server communication

in WebNMS Framework • 9 years ago

Dear all,
I implemented client/server communication with a hard coded key. but i want to assign a unique key for every user so they can communicate with server and vise versa.

At first step i tried to use username as unique key but if user login to nms from two pc, so what's happens?
At second step i tried to use client IP address as unique key but i could not find any API in NMS at client side to determine the real IP address that client connect via it to server.Is any such API exists?
any other solution?
what is the mechanism of NMS for it's communications, as seen there are several 'Registering for response' statement at client start up in console which i think via them client register itself for response from the server via the Sockets. so what is the unique key?

Regards,
JavaGeek

Replies(4)

venkatram.. Employee

Re: Unique key for Client/Server communication

9 years ago

Geek

WebNMS client will have hardcoded string for each module.

If you want to dynamically create the unique if (per client), we recommend you to use NmsClientUtil.sessionId (fyi, NmsClientUtil.getUserName() can also be used if you prefer - but sessionId, which will be the JSession id, will be unique).

Recommended read: Client Server Communication and sample sources in NMS_HOME/default_impl/client_server_communication

Hope this helps.

Regards
Venkatramanan

javageek

Re: Re: Unique key for Client/Server communication

9 years ago

Hi dear Venkatramanan,

I read Client Server Communication section many times.

As i know just after client logged in ,at first step it is the server which register itself for receiving message from client and then client via implementing SocketConnection register itself to receiving message from server. in both side a the unique and same key should be share between client and server. so the server should generate the key and give it to client. but how server can give this key to client? how it can communicate with client? because of this issue i just find the username can be the key. because both the server and the client have it.

Generating a unique key is not the main problem, the main issue is how to share the unique key between client and server.

Regards,

JavaGeek

javageek

Re: Unique key for Client/Server communication

9 years ago

Hi,
I think a have a misunderstanding. I thought each client should have unique key but it seems each class at client side which implement SocketConnection should register itself with a unique key. Am i right?

Regards,
JavaGeek.

venkatram.. Employee

Re: Unique key for Client/Server communication

9 years ago

Yes! You are right.
The response from server will reach the corresponding client based on this ID.

Regards
Venkatramanan

Top Reply

Response title

Attachments

New to this Portal?