Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / lazarus / 2017-10

IPC: TSimpleIPC, ZeroMQ, nanomsg...

8 messages · 4 people · –

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Marcos Douglas B. Santos

Hi,

I would like to know if someone has already worked with Messages between different programs, made in different languages, with binds to work in FPC and Delphi 7.

My main case is connect a old Delphi 7 program to have a "conversation" with others Exes, coded in FPC, locally.

But in the future, I will need to send/receive messages through network, "talking" with Java and C# services.

Some options that I have already seen:
- ZeroMQ -> http://zeromq.org/
- nanomsg -> http://nanomsg.org/

I would like to use a "famous" library, which has good documentation with many binds, or to use the simpler one that allows me to use in all these languages above.

What do you propose?

Best regards,
Marcos Douglas

Reply by email

R0b0t1
to Marcos Douglas B. Santos
Marcos Douglas B. Santos wrote 22 lines
Hi, I would like to know if someone has already worked with Messages between different programs, made in different languages, with binds to work in FPC and Delphi 7. My main case is connect a old Delphi 7 program to have a "conversation" with others Exes, coded in FPC, locally. But in the future, I will need to send/receive messages through network, "talking" with Java and C# services. Some options that I have already seen: - ZeroMQ -> http://zeromq.org/ - nanomsg -> http://nanomsg.org/ I would like to use a "famous" library, which has good documentation with many binds, or to use the simpler one that allows me to use in all these languages above. What do you propose?

I have heard good reviews of ZeroMQ. If you do not actually need full IPC services, then consider that it is not uncommon for developers to roll their own socket/TCP based IPC. Another common variant is socket IPC augmented with memory maps for large amounts of data.

R0b0t1.

Reply by email

Sandro Cumerlato
to R0b0t1

ZeroMQ (libzmq 4.2.2) header binding for FPC is available at:

https://github.com/DJMaster/zeromq-fpc

Best regards.

Sandro Cumerlato

On 19 October 2017 at 05:23, R0b0t1 via Lazarus <

Show quoted text 39 lines
wrote: On Wed, Oct 18, 2017 at 3:38 PM, Marcos Douglas B. Santos via Lazarus wrote: > Hi, > > I would like to know if someone has already worked with Messages > between different programs, made in different languages, with binds to > work in FPC and Delphi 7. > > My main case is connect a old Delphi 7 program to have a > "conversation" with others Exes, coded in FPC, locally. > > But in the future, I will need to send/receive messages through > network, "talking" with Java and C# services. > > Some options that I have already seen: > - ZeroMQ -> http://zeromq.org/ > - nanomsg -> http://nanomsg.org/ > > I would like to use a "famous" library, which has good documentation > with many binds, or to use the simpler one that allows me to use in > all these languages above. > > What do you propose? > I have heard good reviews of ZeroMQ. If you do not actually need full IPC services, then consider that it is not uncommon for developers to roll their own socket/TCP based IPC. Another common variant is socket IPC augmented with memory maps for large amounts of data. R0b0t1. -- _______________________________________________ Lazarus mailing list https://lists.lazarus-ide.org/listinfo/lazarus

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus-ide.org/pipermail/lazarus/attachments/20171019/b46c7850/attachment.html>

Reply by email

Denis Kozlov
to Marcos Douglas B. Santos: I would like to know if someone has already worked with Messages between different…

I would also suggest IPC through TCP/IP.

I have deployed several tools with such IPC implementation which operate across multiple platforms and are rock solid. All you need is a good networking library that works in both FPC and Delphi, such as Synapse <http://www.ararat.cz/synapse/doku.php/download> (make sure to use the latest trunk version). Both Java and C# have extensive TCP/IP components so you will have no problem there.

Also FPC wiki has a list of some networking libraries: http://wiki.lazarus.freepascal.org/Networking_libraries

Denis

Marcos Douglas B. Santos wrote 24 lines
Hi, I would like to know if someone has already worked with Messages between different programs, made in different languages, with binds to work in FPC and Delphi 7. My main case is connect a old Delphi 7 program to have a "conversation" with others Exes, coded in FPC, locally. But in the future, I will need to send/receive messages through network, "talking" with Java and C# services. Some options that I have already seen: - ZeroMQ -> http://zeromq.org/ - nanomsg -> http://nanomsg.org/ I would like to use a "famous" library, which has good documentation with many binds, or to use the simpler one that allows me to use in all these languages above. What do you propose? Best regards, Marcos Douglas

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus-ide.org/pipermail/lazarus/attachments/20171019/4e9b35c9/attachment.html>

Reply by email

Marcos Douglas B. Santos
Denis Kozlov wrote 10 lines
I would also suggest IPC through TCP/IP. I have deployed several tools with such IPC implementation which operate across multiple platforms and are rock solid. All you need is a good networking library that works in both FPC and Delphi, such as Synapse (make sure to use the latest trunk version). Both Java and C# have extensive TCP/IP components so you will have no problem there. Also FPC wiki has a list of some networking libraries: http://wiki.lazarus.freepascal.org/Networking_libraries

Well, we use that way today but some times the performance is not good. So, I am thinking to use our own API but using a new tool for communication between applications. If everything is local, we may improve the performance.

But do you also recommend to use TCP even in local (same machine) applications? How do you know which ports were used for each application? I believe you need to use a local database (SQLite) to register all URLs for each Exe when they started. You might not use hardcode ports because others application could be using first.

Denis Kozlov wrote 15 lines
> But do you also recommend to use TCP even in local (same machine) > applications? Yes, but whether it would be the best method to use will depend heavily on your use case. > How do you know which ports were used for each application? That, again, depends on your use case. For example, if your application needs to create multiple child processes and control them, then the first instance creates a listening server on some predetermined port and each child process will connect to the same predetermined port to talk to the master/server.

But, as I told you, we shouldn't predetermined ports because others processes, which do not belongs us, could use the same ports. I believe, these ports should be dynamic and the main application needs a way to know these informations.

By the way, you have moved this conversation away from the mailing list. Was that intentional?

Not intentional, sorry. I just clicked on reply... So, I am sending to Lazarus now all private emails.

Best regards
Marcos Douglas

Reply by email

Denis Kozlov
to Marcos Douglas B. Santos
But do you also recommend to use TCP even in local (same machine) applications?

Yes, but whether it would be the best method to use will depend heavily on your use case.

How do you know which ports were used for each application?

That, again, depends on your use case.

For example, if your application needs to create multiple child processes and control them, then the first instance creates a listening server on some predetermined port and each child process will connect to the same predetermined port to talk to the master/server.

Denis

Marcos Douglas B. Santos wrote 48 lines
On Thu, Oct 19, 2017 at 4:44 PM, Denis Kozlov wrote: > I would also suggest IPC through TCP/IP. > > I have deployed several tools with such IPC implementation which operate > across multiple platforms and are rock solid. All you need is a good > networking library that works in both FPC and Delphi, such as Synapse (make > sure to use the latest trunk version). Both Java and C# have extensive > TCP/IP components so you will have no problem there. > > Also FPC wiki has a list of some networking libraries: > http://wiki.lazarus.freepascal.org/Networking_libraries Well, we use that way today but some times the performance is not good. So, I am thinking to use our own API but using a new tool for communication between applications. If everything is local, we may improve the performance. But do you also recommend to use TCP even in local (same machine) applications? How do you know which ports were used for each application? I believe you need to use a local database (SQLite) to register all URLs for each Exe when they started. You might not use hardcode ports because others application could be using first. On Fri, Oct 20, 2017 at 12:24 PM, Denis Kozlov wrote: >> But do you also recommend to use TCP even in local (same machine) >> applications? > Yes, but whether it would be the best method to use will depend heavily on > your use case. > >> How do you know which ports were used for each application? > That, again, depends on your use case. > > For example, if your application needs to create multiple child processes > and control them, then the first instance creates a listening server on some > predetermined port and each child process will connect to the same > predetermined port to talk to the master/server. But, as I told you, we shouldn't predetermined ports because others processes, which do not belongs us, could use the same ports. I believe, these ports should be dynamic and the main application needs a way to know these informations. > By the way, you have moved this conversation away from the mailing list. Was > that intentional? Not intentional, sorry. I just clicked on reply... So, I am sending to Lazarus now all private emails. Best regards Marcos Douglas

Reply by email

Denis Kozlov
to Marcos Douglas B. Santos: Well, we use that way today but some times the performance is not good. So, I am thinking…
Marcos Douglas B. Santos wrote
But, as I told you, we shouldn't predetermined ports because others processes, which do not belongs us, could use the same ports. I believe, these ports should be dynamic and the main application needs a way to know these informations.

You can minimize the possibility of interference by avoiding the use of well-known and registered ports:
https://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbers

Option 1: Pick some obscure port, for example 12375 (I just made it up).

Option 2: Your server can attempt to bind to a range of commonly free ports, pick the first open port and write it to a file or registry or other location that can be read by potential clients.

Denis

Reply by email