Correct way to make a client run

[juanbg]

Hi guys, sorry for ask this on here, but I can't found any other way to get communication with you.

I'm developing a system which goal is user interfaces supply when a sensor detects a change.

I'm thinking about give the next structure to the application:

• Router & Client in backend application with all methods to get correct ui based on user interactions.
• Client detecting sensor changes, and try to get the correct ui.

Reading the documentation provided by wamp-proto.org I could use RPC maybe to call a method which returns the correct ui and the settings for that. Or use SUB/PUB, to suscribe my router & client to my only client, and wait for publication of any sensor change.

What do you think could be the best solution, thinking in performace?

And looking through exaples, I've seing that clients connected to external routers running for ever with infinite loops or some like that. That is the correct way? Or is better close and open again based on my interactions?.

the last is, I made my only client, and I noticed that it cannot connect, I need to made a thread run to get more time and let it connect. Is that correct too?

Thanks for the time.