hikalkan / scs

TCP Server/Client Communication and RMI Framework
MIT License
225 stars 112 forks source link

Connect a hosted TCP service #33

Open Abhijeet310187 opened 6 years ago

Abhijeet310187 commented 6 years ago

Hi,

We have a logging service hosted in our infrastructure, that is built using HIK SCS library.

Is it possible to connect to the service normally without HIK SCS client?

I am getting issues.

hikalkan commented 6 years ago

Is it possible to connect to the service normally without HIK SCS client?

Yes, possible if you can implement the same protocol on the pairing application. You can understand protocol (used BinarySerializationProtocol by default) from the document (https://www.codeproject.com/Articles/155282/A-Complete-TCP-Server-Client-Communication-and-RMI) and source code.

Hint: See to understand the message format of the BinarySerializationProtocol class:

https://github.com/hikalkan/scs/blob/master/src/Scs/Communication/Scs/Communication/Protocols/BinarySerialization/BinarySerializationProtocol.cs#L60

There is a 4-bytes "message length" followed by the binary serialized object (for each message).

Abhijeet310187 commented 6 years ago

Thank you Halil,

I will give it a try.

Regards, Abhijeet

On Tue, May 15, 2018 at 11:12 PM, Halil İbrahim Kalkan < notifications@github.com> wrote:

Is it possible to connect to the service normally without HIK SCS client?

Yes, possible if you can implement the same protocol on the pairing application. You can understand protocol (used BinarySerializationProtocol

https://github.com/hikalkan/scs/blob/master/src/Scs/Communication/Scs/Communication/Protocols/BinarySerialization/BinarySerializationProtocol.cs by default) from the document (https://www.codeproject.com/ Articles/155282/A-Complete-TCP-Server-Client-Communication-and-RMI) and source code.

Hint: See to understand the message format of the BinarySerializationProtocol class:

https://github.com/hikalkan/scs/blob/master/src/Scs/Communication/Scs/ Communication/Protocols/BinarySerialization/BinarySerializationProtocol. cs#L60

There is a 4-bytes "message length" followed by the binary serialized object (for each message).

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/hikalkan/scs/issues/33#issuecomment-389161379, or mute the thread https://github.com/notifications/unsubscribe-auth/AQO19thjrDlaPeBYjQ5dGauuaPauP1yfks5tytRQgaJpZM4T-wMI .