Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 6 days ago.
Improve this question
Good Morning
We have the follow architecture:
=> Scanner take picture of Serial Numer and send to Client PC
=> Client PC send the serial number by RMI (JAVA) to Server.
=> Server check the data, send a confirmation by OPC XML DA Client to the MicroBox
=> MicroBox (IPC) get confirmation by OPC XML DA server and send by Profinet to ET200 (configure with SIMATIC NET)
=> ET200 automaton set the PNIO and send information to Conveyor by SMEMA Protocol
=> Conveyor Stop/Start the line
Problem is that OPC XML DA is old and not supported.
So we are looking to replace it !
Which communication protocol is the best for use in this case ?
OPC UA
API REST
MQTT
Thanks in advance for answer.
It's for advice on the comunication protocol use for my application.
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
Good day stackoverflow. Presently I have a java server program which communicates with the client application through sockets(using the java ServerSocket and Socket classes). But I intend to develop another client application with an interface for configuring the server application, for which I would like to use RMI(Remote Method Invocation).
The question now is: is it possible and safe to use RMI in a java server program in which ServerSockets and Sockets are also being used? I am familiar with sockets good enough but new to RMI. I have gone through RMI documentation and other sources but got no answers yet. Please I would be obliged if someone can help
Yes, no problem. Just make sure you are not using the same sockets.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
Java Applets support socket but limits the connection towards the
http server from which the applet has been downloaded.
Why a WebSocket abstraction has been created for sending data
from Javascript/HTML 5 ? Wouldn't have been possible to add support
for a “classical” socket in JS and limit the connection (as it
has been done for Java Applets)
Because WebSocket starts as a HTTP request, therefore it is easier to go through firewalls and other inspectors. Also, such HTTP negotiation can do HTTP operations like sending/retrieving cookies from the browser for example, which provides a nice integration with the rest of the web application.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
I'm looking at WebRTC and I'm wondering how to implement a solution where the client connects to the PTSN via SIP. It seems like a pretty new technology so I assume that this would not work on IE browsers; is this correct?
Basically, I have a dialpad UI on the page and users who have an SIP account. Can WebRTC enable the end-user to make calls to the PTSN and what does it take to implement such solution?
I'm looking into this as an alternative to Java or Flash based webphones.
Thanks for your suggestions.
WebRTC is indeed new and isn't available on IE or Safari. It is available in beta/alpha on other browsers. IE will probably support it in the future and Safari probably won't for some time.
WebRTC does only the media parts of the negotiation, and as such it means that it does no signaling of its own. SIP can work well with WebRTC, but you will need a JS implementation of SIP (over WebSockets) and then you'll need to unwrap the SIP signaling on the server side and "migrate" it to UDP or TCP.
Asterisk are working on such a server side platform: http://blogs.digium.com/2012/05/23/asterisk-11-webrtc/
More about doing SIP in conjunction with WebRTC can be found here: http://bloggeek.me/html-sip/
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
I want to create a chatting application that enable users that connect via XMPP to chat with another users that connect using web socket (perhaps using Netty or Jetty) or vice versa. So every users that connect using web application can chat with other user that connect using web socket.
I am not sure that websocket currently have a default standard that enable it to communicate with other protocols. Let me know your opinion and suggestion.
Very much like on top of TCP, you can implement rich business protocols over WebSockets as well. Kaazing offers XMPP as one of several protocols over WebSockets (in addition to JMS and AMQP).
You can check out the XMPP edition of the Kaazing WebSocket Gateway here, and find the documentation and tutorials here. The developer version of the product, up to 50 concurrent connections, is a free download. The community edition is open-source licensed under the Apache 2.0 license.
There exists a draft for XMPP over WebSockets. It's a year since it was submitted, but I think work on it will continue once WS itself stabilizes.
There exists experimental implementations of XMPP over WS, but since WS has been a moving target, they aren't implementing the latest versions (AFAIK).
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 5 years ago.
Improve this question
I am looking to write a simple client/server utilizing TCP sockets. Any ideas how to do network programming in Go?
Go has fine support for networking.
For a server, the easiest thing to do is have your main() start a tcp accept loop and spawn a goroutine to handle each request.
The first go software I wrote was a memcached server. You may want to check out gomemcached for an idea of how to get started on servers.
Clients shouldn't be particularly harder. In many cases, it may make the most sense to have a shared client with goroutines for inbound communication much like I use in gomemcached for communicating with the actual storage layer.
Of course, this isn't the only way. Perhaps you'll find something better as you experiment.