Communication between two different rebol apps
[1/4] from: ale870::gmail::com at: 21-Jun-2006 17:02
Hello, I have a problem: I have two different rebol programs running on the same PC. How can I let them communicate WITHOUT using sockets? I wish to avoid to use sockets since I don't want to block some ports. But now, I cannot find any other alternatives. MASTER-APPLICATION \____ APPLICATION 1 \_____APPLICATION 2 \_____APPLICATION 3 Have you any idea? (if not, I will implement Jell Console Manager using local PC sockets). Thank you! --Alessandro
[2/4] from: petr:krenzelok:trz:cz at: 21-Jun-2006 17:31
First, Alessandro, you should really join AltME with your ideas and activity. Not everybody is watching ml and you get more input on AtlME.
> I have a problem: > I have two different rebol programs running on the same PC. How can I > let them communicate WITHOUT using sockets? >
Why without sockets? Is opening a listen port a problem on such a machine? E.g. a firewall issue?
> I wish to avoid to use sockets since I don't want to block some ports. > But now, I cannot find any other alternatives. > > MASTER-APPLICATION > \____ APPLICATION 1 > \_____APPLICATION 2 > \_____APPLICATION 3 >
I once proposed following scenario for my friend, using directories: App1 \from-app2 \from-app3 App2 \from-app1 \from-app3 App3 \from-app1 \from-app2 The idea was for each app to own its own directory. For stuff from other apps, it would look into particular subdirectory. If app1 on the other hand wants to tell something to app2, it writes to app2\from-app1 directory. You can come up with whatever schema makes sense to you :-) To keep things in track a bit, use timestamps for particular files. Use IOS kind of aproach - one message = one file. It all depends upon how complicated your communication is going to be ...
> Have you any idea? > > (if not, I will implement Jell Console Manager using local PC sockets). >
What do you mean local pc sockets and how do you want them to utilise from Rebol? Cheers, -pekr-
[3/4] from: ale870:gm:ail at: 21-Jun-2006 17:51
Hi Petr, First of all: I tried to use altme, but I could not use user/pwd and group. It seems only group for Rebol 3 is up, and it is a reserved group. Can you help me to enter in the group you are talking about? Thank you! Second item: Jell Console Manager let you use Rebol from a client to remote server. Every client can open a different window (such a console-shell) then you can type commands: those command will be executed on remote server (I putted 3 small screenshots about the application): http://ale870.pbwiki.com/f/login.jpg http://ale870.pbwiki.com/f/commands1.jpg http://ale870.pbwiki.com/f/commands2.jpg But it means on the client-side you can open as many console you want (e.g.: you can have 3 consoles: TWO consoles connected to server 18.104.22.168 and ONE connected to server 22.214.171.124). My final target is every client console talks to the server using a single socket server (e.g.: port 80...) and the server-side takes the request and forward it to the right server-instance. SERVER-INSTANCE: every console client dynamically creates a console-server-instance. CLIENT1 --> MASTER-SERVER(COMPUTER 1) --> SERVER INSTANCE 1 CLIENT2 --> MASTER-SERVER(COMPUTER 1) --> SERVER INSTANCE 2 CLIENT3 --> MASTER-SERVER(COMPUTER 2) --> SERVER INSTANCE 1 As you can see, MASTER SERVER communicates with LOCAL server instances in REAL-TIME. I wanted to avoid to use sockets for this communication. It is a little bit complex to explain it via email, but I hope I was enough clear. I'm sure this concept works VERY WELL (screenshots are a true running application). On 6/21/06, Petr Krenzelok <petr.krenzelok-trz.cz> wrote:
[4/4] from: greggirwin::mindspring::com at: 21-Jun-2006 10:19
Hi Alessandro, AM> First of all: I tried to use altme, but I could not use user/pwd and group. AM> It seems only group for Rebol 3 is up, and it is a reserved group. AM> Can you help me to enter in the group you are talking about? Thank you! I'll set you up an account. -- Gregg