V
Veeresh Angadi
Guest
Hi All,
We have a requirement to implement both TCP communication and Websockets in a single service. The requirement is like we have a service which will act as Server for both TCP and Websocket communication. TCP is used connect devices to our service. Web socket is used to send device data back to registered clients. When there is any event on device, device will send respective data to our service.
Web socket client should connect to same service and register to events from a specific device. When there is a event on device, our service will receive data and process it. The processed data will be sent back to registered web socket clients.
I know how to implement all this but my question is can we achieve this in single service? To make Web socket service available over network, we have to host it in IIS. In one of the blog i read that TCP communication(with devices) in IIS is not a good option.
Veeresh Angadi
Continue reading...
We have a requirement to implement both TCP communication and Websockets in a single service. The requirement is like we have a service which will act as Server for both TCP and Websocket communication. TCP is used connect devices to our service. Web socket is used to send device data back to registered clients. When there is any event on device, device will send respective data to our service.
Web socket client should connect to same service and register to events from a specific device. When there is a event on device, our service will receive data and process it. The processed data will be sent back to registered web socket clients.
I know how to implement all this but my question is can we achieve this in single service? To make Web socket service available over network, we have to host it in IIS. In one of the blog i read that TCP communication(with devices) in IIS is not a good option.
Veeresh Angadi
Continue reading...