Re: [racket-users] How to integrate Racket with a .Net application?

[HiPhish]

For the people not following my bug tracker: I fixed it now.

On Friday, February 2, 2018 at 2:44:25 PM UTC+1, berthold.baeuml wrote:
>
> https://pkgs.racket-lang.org/package/msgpack is a nice package to use. 
> Thank you for providing it. But there is a bug for sequence lengths  >15 
> and <255. I filed an issue at 
> https://gitlab.com/HiPhish/MsgPack.rkt/issues/4
>
> Berthold
>

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [racket-users] How to integrate Racket with a .Net application?

[Berthold Bäuml]

https://pkgs.racket-lang.org/package/msgpack is a nice package to use. Thank 
you for providing it. But there is a bug for sequence lengths  >15 and <255. I 
filed an issue at https://gitlab.com/HiPhish/MsgPack.rkt/issues/4

Berthold


> On 2. Feb 2018, at 01:04, HiPhish  wrote:
> 
> On Wednesday, January 31, 2018 at 4:17:09 PM UTC+1, Greg Hendershott wrote:
> Another way is for two (OS) processes to "pipe" I/O to each other. 
> 
> This is a great idea since it would allow to integrate any language with the 
> .NET application. It is how Neovim does it: the main application is Neovim, 
> which is written in C, and it acts as a server for a client application 
> written in whatever other language. The protocol used is MessagePack RPC:
> https://github.com/msgpack-rpc/msgpack-rpc/blob/master/spec.md
> 
> It is built on top of the MessagePack serialisation format. In a nutshell, 
> MessagePack is like JSON, but binary. This makes it smaller to transport and 
> faster to pack and unpack, but it loses the nice human-readability of JSON. I 
> think that's a good tradeoff for data that is not meant to be stored and 
> manipulated by a person, but instead passed around between processes.
> https://msgpack.org/
> 
> I have already written a general-purpose MessagePack library for Racket, as 
> well as a language client for Neovim:
> https://pkgs.racket-lang.org/package/msgpack
> https://pkgs.racket-lang.org/package/nvim-client
> 
> The MessagePack library is safe to use. The Neovim client is my first time 
> doing something with RPC, so I'm not yet ready to call it stable. The part of 
> the codebase which implements MessagePack RPC is not entangled with the 
> Neovim-specific parts, so once the language client matures it will be easy to 
> take it out and make it into a general-purpose MessagePack RPC library.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Racket Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to racket-users+unsubscr...@googlegroups.com 
> .
> For more options, visit https://groups.google.com/d/optout 
> .

-- 
---
Berthold Bäuml -- Head of Autonomous Learning Robots Lab
DLR, Robotics and Mechatronics Center (RMC)
Münchner Str. 20, D-82234 Wessling
Phone +49 8153 282489
http://www.robotic.de/Berthold.Baeuml 

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [racket-users] How to integrate Racket with a .Net application?

[HiPhish]

On Wednesday, January 31, 2018 at 4:17:09 PM UTC+1, Greg Hendershott wrote:
>
> Another way is for two (OS) processes to "pipe" I/O to each other. 
>

This is a great idea since it would allow to integrate any language with 
the .NET application. It is how Neovim does it: the main application is 
Neovim, which is written in C, and it acts as a server for a client 
application written in whatever other language. The protocol used is 
MessagePack RPC:
https://github.com/msgpack-rpc/msgpack-rpc/blob/master/spec.md

It is built on top of the MessagePack serialisation format. In a nutshell, 
MessagePack is like JSON, but binary. This makes it smaller to transport 
and faster to pack and unpack, but it loses the nice human-readability of 
JSON. I think that's a good tradeoff for data that is not meant to be 
stored and manipulated by a person, but instead passed around between 
processes.
https://msgpack.org/

I have already written a general-purpose MessagePack library for Racket, as 
well as a language client for Neovim:
https://pkgs.racket-lang.org/package/msgpack
https://pkgs.racket-lang.org/package/nvim-client

The MessagePack library is safe to use. The Neovim client is my first time 
doing something with RPC, so I'm not yet ready to call it stable. The part 
of the codebase which implements MessagePack RPC is not entangled with the 
Neovim-specific parts, so once the language client matures it will be easy 
to take it out and make it into a general-purpose MessagePack RPC library.

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [racket-users] How to integrate Racket with a .Net application?

[Greg Hendershott]

Another way is for two (OS) processes to "pipe" I/O to each other.

The back-and-forth "protocol"?

It could be as simple/ad-hoc vs. as formal/ceremonial as you prefer.

It could be text line-oriented, or JSON, or s-expressions, or raw bytes.


I might use this as a starting point, get some mileage, then decide if
it's adequate or what to do instead.

p.s. If you squint and abstract away certain details, this is similar
to the HTTP service approach.

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.