| Re: [milo-dev] OPC-UA server implementation clarification |
Milo implements the OPC UA TCP transport and OPC UA Binary serialization. This is the only mandatory transport and is the only one I've seen widely used in industry. The SOAP transport as actually deprecated as of the OPC UA 1.03 and will likely never be implemented in Milo.> If a OPC server is written in Java and TCP can it be accessed by a C# client and vice versa?Yes, absolutely.> Does different Java Server implementations need unique Java client implementations each? or one Java client implementation can be used to connect with various type of Java server implementations by different vendors?Any implementation, in any language, from any vendor, should be able to interoperate with each other. That's largely the entire purpose of OPC UA.On Fri, Nov 10, 2017 at 12:22 AM, Isuru Samaraweera <isuru@xxxxxxxx> wrote:______________________________Hi All,Can somebody please clarify the below?
- OPC spec says it should support TCP/(SOAP,HTTP)/HTTPS protocols.Which protocols are mandatory to support and which one's are optional?
- If a OPC server is written in Java and TCP can it be accessed by a C# client and vice versa?
- Does different Java Server implementations need unique Java client implementations each? or one Java client implementation can be used to connect with various type of Java server implementations by different vendors?
- If above is yes then there has to be common language like WSDL?Is it?
Please clarify the aboveThanksIsuru_________________
milo-dev mailing list
milo-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/milo-dev
_______________________________________________
milo-dev mailing list
milo-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/milo-dev