I can also attest that connecting a Julia process to other processes with
ZeroMQ is a very good way to go – it's reliable and easy and quite
efficient. ZMQ gives many side benefits too. Probably easier than
developing a full-blown REST interface, imo.

On Wed, Dec 17, 2014 at 8:43 PM, Steve Kelly <[email protected]> wrote:

> I am currently building a path planner for 3D printers in Julia. We are
> also using a ZeroMQ interface to separate the web interface from the path
> planner. This is working very well for us now. We will also be using
> JuliaBox for packaging our application.
>
> On Wed, Dec 17, 2014 at 8:05 PM, Eric Forgy <[email protected]> wrote:
>>
>> Thank you Viral and thank you Stefan.
>>
>> The Rust solution would be an interesting and longer term effort because
>> the person I would rely on to do most of the development is not yet ready
>> to take the Rust plunge until it matures/stabilizes a bit more.
>>
>> The other two ideas REST and zeromq look interesting and I'd like to
>> learn more. I spent what little available time I had yesterday reading
>> about message queueing with zeromq and others. That is very interesting
>> stuff. I had a quick look at JuliaBox. That is pretty awesome :) I would
>> love to understand how it works. Like I said, I am pretty much a blank
>> slate and learning everything as I go, so looking at the JuliaBox code, it
>> wasn't immediately obvious (.t? .lua? :)). Does there exist a simple
>> document describing the process flow of how JuliaBox works?
>>
>> In very general terms, could you help sketch out and point me to some
>> reading material to help me make progress building a RESTful interface to
>> Julia running on a server? Should it be built entirely in Julia? Is it
>> already done in JuliaBox or elsewhere? I think initially, I will focus on
>> REST. Another platform (OpenGamma) I'm working with also has a RESTful API
>> so any effort I make will not be wasted even if I eventually start work
>> with zeromq (which I probably will).
>>
>> Thank you again.
>>
>> Cheers,
>> Eric
>>
>>

Reply via email to