Hi Viral,

Thanks for pointing out JuliaBox.jl. I wasn't aware of this. I'm building 
something similar with Morsel :)

I'm making HTTP/RESTful calls to a Julia server from javascript and 
displaying results using d3, e.g. 


<https://lh5.googleusercontent.com/-cKLcAUQsjTY/VN8dUfY0QcI/AAAAAAAAAIQ/_4v65VfGpIE/s1600/Screen%2BShot%2B2015-02-14%2Bat%2B6.01.58%2Bpm.png>



This is running on a Morsel server, calls Julia's "rand" with arguments 
from the query string, returns the result in JSON format, and plots it.

We should compare notes! :)

Best regards,
Eric


On Saturday, February 14, 2015 at 5:30:44 PM UTC+8, Viral Shah wrote:
>
> There is also JuliaBox.jl (https://github.com/tanmaykm/JuliaBox.jl), 
> which facilitates wrapping of julia functions into a remote callable HTTP 
> or ZMQ API. I think the package name is a bit misleading, and perhaps 
> something like JuliaRemoteAPI or something may be more meaningful.
>
> The thought was that for JuliaBox users, we can make it easy to deploy any 
> julia function behind an HTTP API. 
>
> -viral
>
>
> On Friday, February 13, 2015 at 4:27:56 AM UTC+5:30, Iain Dunning wrote:
>>
>> Hi all,
>>
>> TL;DR: 
>> - New JuliaWeb "roadmap": https://github.com/JuliaWeb/Roadmap/issues
>> - Please consider volunteering on core JuliaWeb infrastructure (e.g. 
>> Requests, GnuTLS), esp. by adding tests/docs/examples.
>>
>> ---
>>
>> *JuliaWeb* (https://github.com/JuliaWeb) is a collection of 
>> internet-related packages, including HTTP servers/parsers/utilities, IP 
>> address tools, and more.
>>
>> Many of these packages were either created by rockstar ninja guru 
>> developer Keno, or by students at "Hacker School". Some of these packages, 
>> like Requests.jl/HttpParser.jl/GnuTLS.jl/... are almost surely installed on 
>> your system, but some (e.g. GnuTLS.jl) haven't really been touched much 
>> since they were created and aren't actively maintained. For such core 
>> packages, it isn't fair to put all the burden on one developer.
>>
>> On a personal level, I've been trying to help out where I can by merging 
>> PRs, but this web stuff isn't really my strength, and I'm not really able 
>> to effectively triage the issues that have built up on some of these 
>> packages. So heres what we're (Seth Bromberger has been part of this 
>> too) doing:
>>
>> - We've made a *"roadmap" repo for JuliaWeb* to discuss some of these 
>> issues and co-ordinate limited resources: 
>> https://github.com/JuliaWeb/Roadmap/issues . We'd like to hear your 
>> perspectives!
>>
>> - *We want you!* You don't have to be a Julia master - you can even 
>> start just by reading the code of one of these packages, and then adding 
>> some tests or documentation. Maybe you'll even get comfortable to add 
>> features! Right now, the focus is definitely on maintainence and making 
>> sure whats there works (on Julia 0.3 and 0.4!). Your Pull Requests are very 
>> welcome!
>>
>

Reply via email to