A better IPC Protocol

[gabrielrcouto]

We can use a better IPC Protocol, it need to be:

• Faster to encode/decode
• Use less memory
• Easy to split a big message
• Binary (no need to be human readable)

Suggestions:

• https://github.com/google/flatbuffers
• https://github.com/google/protobuf
• https://capnproto.org/
• http://mechanical-sympathy.blogspot.com.br/2014/05/simple-binary-encoding.html

A great comparison: https://capnproto.org/news/2014-06-17-capnproto-flatbuffers-sbe.html

[ghost]

I'm not sure about splitting big data, but msgpack might be an option.

[qbitza]

Switching to BSON would be fairly easy when combining the Pascal side to mORMot. Or use anything STOMP based: https://en.wikipedia.org/wiki/Streaming_Text_Oriented_Messaging_Protocol

[gabrielrcouto]

Well, I did some tests:

• capnproto/protobuf/msgpack doesn't have a good Free Pascal implementation
• all alternative PHP encoders are slower than json if we use a pure PHP implementation (and not an extension)

We can see some bench for PHP encoders HERE and HERE.

[reisraff]

Take a loot in #104

[PeratX]

Use a binary stream xD

[Gold-Samiar]

I found few problems in communication between PHP and Pascal. There are no data type conversion in protocol. Pascal is more hard so it need more information before process any code. There are no dynamic call in Pascal side so limited development. My suggestion is that the protocol should have value:datatype format which can convert on pascal side. JSON data type is always string but pascal may need widestring datatype so we can write value:widestring. in this we need less code on pascal side and can fix basic datatypes conversion.