search for: restrserve

Thanks for the quick responses. As you both suggested storing the packages to local drive is feasible but comes with a size restriction I wanted to avoid. I'll keep this in mind as plan B. @Hugh: 2. would impose even greater slowdowns and 4. is just not feasible. However, 3. sounds interesting - how would this work in a Linux environment? Thank you, Mario Am So., 19. Juli 2020 um 20:11 Uhr

...fancy docs but it has been widely used. In essence, R runs "headless" and connect to it (think "telnet" or "ssh", but programmatically), fire off request and get results with zero startup latency. But more work to build the access layer. And Rserve is also underneath RestRserve which allows you to query a running server vai REST / modern web stack tech. (Think "plumber", but in C++ and faster / more scaleable). Lastly, there is Jeroen's OpenCPU. Dirk -- https://dirk.eddelbuettel.com | @eddelbuettel | edd at debian.org

...nnection, other may want co-operation in a separate environment. It is all doable, but beyond the scope of R's internal http server. Moreover the internal http server is based on the Rserve package and you always have much larger flexibility there. There are also higher level abstractions like RestRserve. So if you like the internal server then you can seamlessly use Rserve as the API was derived from there. Of course there are other alternatives in package space like httpuv. We typically don't want to fold things into core R unless it's absolutely necessary - i.e., if they can happily live...

...other may want co-operation in a separate environment. It is all doable, but beyond the scope of R's internal http server. > > Moreover the internal http server is based on the Rserve package and you always have much larger flexibility there. There are also higher level abstractions like RestRserve. So if you like the internal server then you can seamlessly use Rserve as the API was derived from there. Of course there are other alternatives in package space like httpuv. We typically don't want to fold things into core R unless it's absolutely necessary - i.e., if they can happily live...

...rate environment. It is all doable, but >> beyond the scope of R's internal http server. >> >> Moreover the internal http server is based on the Rserve package and >> you always have much larger flexibility there. There are also higher >> level abstractions like RestRserve. So if you like the internal server >> then you can seamlessly use Rserve as the API was derived from there. >> Of course there are other alternatives in package space like httpuv. >> We typically don't want to fold things into core R unless it's >> absolutely ne...

R has a native HTTP server that is used for serving R help pages interactively, at least on the loopback device (127.0.0.1) But all of the working are internal, not exposed to user and not documented. This is quite shame since the server seems to be fully capable of handling basic tasks, be it serving static websites or even interactively processing queries. This was previously noticed by