REBOL IPC, new era of communication ...

Hi, so we have nicely advanced Rebol View now. Maybe it is a time to think a little bit about where do we want rebol to go. Although I strongly believe Carl and his team knows what they would like to add to Rebol Core and other layers, let me express some generel thoughts: 1) although I hadn't followed "web semantics" thread, I think it should not be so difficult to introduce new, dialect based communication standards to rebol world. I was inspired by Express communication dialect - very nice work. First phase could be called - negotiation. Two rebols would exchange/negotiate protocol set-up, e.g. make object! [ protocol-name: 'easy-talk protocol-version: 1.02 compatibility: [1.01 1.00] allow-upgrade-if-newer: true protocol-home: http://www.rebol.com/certified-protocols/communication/easy-talk.r encryption: true encyption-type: RSA compression: true ] After completion of negotiation phase, two rebol apps could commuinicate via dialect. Imagine possible efficiency! - domain specific dialecting ... 2) (not only) In regards to above, two rebol precesses could be linked via TCP kind of IPC. Rebol session which 'launches other Rebol session, would establish tcp socket connection port somewhere in rebol/ports (e.g. field called 'rebol-net). RT could standardise some TCP port number which would be used by Rebol sessions to allow communication. This way, Rebol session would know about its launcher, brothers/sisters (via parent proces - launcher), could send requests, could be closed by parent, and in some future even some kind of load-balancing could be established ... Maybe I am just a dreamer, but I think it is achievable, could be done by RT to have standard (important factor), and it would take Rebol platform to another level in regards to messaging! Carl? :-) Cheers, -pekr-