[Zero]

Hi guys, don't hit me 

How would you share data in windows efficiently?

Shared memory via file mapping?

The aim would be to connect heterogeneous programs, each of which would be providing some part-of-mind service, and unify it all around a (hopefully) conscious core.

I have this page:
https://msdn.microsoft.com/en-us/library/windows/desktop/aa365574(v=vs.85).aspx

Any thought? (I mean, beyond the inevitable "switch to some real OS")

[Art]

Zero,

Interesting page.  Are you wanting this structure or construct to remain only locally available to just one network or one person or for it to be / become much larger or even on a Cloud level, across various divides?

Sounds like so many possibilities are in the mix.

One thing that always concerns me is Security (or lack of), especially when exchanging or adding to the data flow within the construct.
(hackers be everywhere)

[Korrelan]

Shared Ram Drive perhaps? Or write a custom encrypted network protocol?

 

[Zero]

No, that would be local to the machine, so no cluster, no LAN, no nothing. I'll go even further: I always want my stuff to work fine offline.

No it's really: how do I share among processes on 1 machine, at very high speed. On windows. Tough stuff for me, I'm completely new to this.

I want to avoid bottlenecks, but I want to be open to existing works that would eventually "plug in" to this system. For instance NLP in python, ivan's works on grammar and parsing, Korrelan's nnets (ok the thing is too huge to fit, but maybe a derived system), an upper ontology thing à la Cyc, ...etc. I want streams between parts, and feedback to the core.
There's ROS on linux and other alternatives. I'm also considering message oriented middlewares like ZeroMQ.

Very open question, I know. Maybe too open, sorry.

[Korrelan]

Writing efficient muti-thread code can be a pain especially when developing software from scratch.

Perhaps write for a fast single thread with an fast network protocol. Use something like oracle virtual machines to simulate a 4 core/ 4 PC network on one machine. The same tech can then easily be expanded to cover real network machines when required. This is similar to what I've done.

 

[keghn]

This logic, IPC, would have to be on the same slab of silicon. Because if you have 20 cpu on this chip then they would need 20 access point in to one memory location. the all write to this location at one time it could be a problem. But all cpu's or gpus's
 reading from on location at one time would not be a problem. This would be very high speed. But it is a more complex.
 I would thing AMD or INtel would be more behind this then MicroSoft.

[Zero]

I want a software solution, because it should be possible to install it simply on any windows 10 machine. You know, the windows way: download, one-click install, icon appears on the desktop.

Libuv (the networking machinery behind nodejs) is a possible path. And, it's C.

[ranch vermin]

share data between windows applications?   im not sure what you are wanting.

[Zero]

What's not clear?

EDIT: I'll try to expand.

Nobody found the whole AGI solution yet. But I believe there are parts of solutions here and there, implemented in different languages. And there might be, in the future, other parts of solutions implemented in various languages. I want to create a message-oriented middleware, on Windows, that could unite several stand-alone programs, no matter what they're made of, around a core that would be simultaneously message broker and think machine. I'll make the core, and try to make it conscious (always feeling what's happening inside of itself) and self-aware (knowing that itself is a specific part of the world). That's the plan. Back to reality, I want fast data sharing between processes. That could be using named pipes, file mapping, or simply TCP, or anything else. I post here, hoping to receive advices from more experienced devs.

[keghn]

Basic Guide of Interprocess Communication and Pipes: 

http://technotif.com/basic-guide-interprocess-communication-pipes/

[keghn]

Socket Programming Tutorial In C For Beginners | Part 1: 

[Zero]

Basic Guide of Interprocess Communication and Pipes: 

http://technotif.com/basic-guide-interprocess-communication-pipes/

Nice link, thank you.

[Zero]

Maybe I should stick to node-ipc. Maybe I'm fooling myself, pretending to search the right tech for the job, when in fact I'm screwin around to avoid, or at least delay, the big jump.

It's a war on yourself.

[Korrelan]

Ahhh… I’m back at my main machines so I can type comfortably… I hate typing on a phone lol.

Use FREE Oracle VirtualBox…

https://www.virtualbox.org/

To create a sand boxed local network of virtual M-XP machines. 

Micro XP is a cut down version of XP that runs much faster and uses far fewer resources.  You can get the MXP.iso at the link below. (Go to main YouTube page)



Once you have your XP network established on your single machine you can experiment with using pipes/ TCP/ UDP protocols safely to create your software. 

If you share a RAM drive on the Host machine and connect the virtual machines over the simulated network you can quickly exchange data (MPI and flagging) between the groups.

If you write your code to efficiently share & utilize the sand boxed virtual windows machines on this network then you can later easily expand to a real network of machines.

This approach will give you a FREE easy way to develop your network based systems.

Cheap four core machines are readily available these days for as little as £40 (UK) so you could quickly and cheaply build a cluster or connect existing networked infrastructures.



 

[keghn]

 I am interested in IPC  because of the failure of USB easy to use software. I need to communicate with may Raspberry PI 3
boards. Can not wait for the Raspberry to upgrade to gigabit  Ethernet  on next board.