Unfortunately that's exactly what I'm trying to avoid as while that will work
just fine for desktop windows as I can separate the processes easily enough
there and just have them talk via any of the many protocols(you guys mentioned)
for conversing between 2 separate binary's on the same system
Agreed. If you have rock-solid Google's Protocol Buffers
implementations on both ends, their schema formalism works for you, and
you don't mind the protocol being harder for a programmer to eyeball in
most tools than sexp/JSON, then (the unfortunately-named :) Protocol
Buffers is a great optio
I've had very good success with Google's protocol buffers standards in Racket:
https://planet.racket-lang.org/display.ss?package=protobuf.plt&owner=murphy&changerep=2
http://voidstarzero.ca/post/137911090363/getting-started-with-protocol-buffers-in-racket
https://developers.google.com/protocol-buf
I don't know about Microsoft UWP specifically, but, FWIW, there is a
long tradition, in various platforms, of partitioning into two or more
host OS processes, and doing some kind of interprocess communication
(IPC) between them. The IPC can be over domain sockets, shared memory,
stdio/TTY, TCP
Has anyone tried/started getting racket up and running as the back end embedded
into a universal windows platform app?
Aka using xaml to layout the gui and using racket for all the thinking bits
--
You received this message because you are subscribed to the Google Groups
"Racket Users" group.
5 matches
Mail list logo
