# Whither rApache and Rook (for R)

**awaiting assimilation**, and kindly contributed to R-bloggers]. (You can report issue about the content on this page here)

Want to share your content on R-bloggers? click here if you have a blog, or here if you don't.

The above picture shows what an apache child process will look like once I add Rook support to rApache. An explanation of the above:

1) The light-orange colored box describes the apache process space.

2) Everything in blue, whether light-blue or cyan, is part of the R process space.

3) mod_R is the rApache portion: it glues together Apache to R.

4) The smaller rectangles (containing the text “brew::brew” and “/path/to/app.R::handler”) represent the current way rApache runs your web applications. Note that these applications will ONLY run via rApache and not any other web server.

5) The cyan ovals represent the new way in which rApache will run Rook applications. ANY Rook (for R) applications, even if you developed it on your desktop.

So, any R web application developed using rApache will only work on rApache, while any R web application using the Rook specification/interface/package will work on rApache or any other Rook-enabled web server, like Rhttpd.

**leave a comment**for the author, please follow the link and comment on their blog:

**awaiting assimilation**.

R-bloggers.com offers

**daily e-mail updates**about R news and tutorials about learning R and many other topics. Click here if you're looking to post or find an R/data-science job.

Want to share your content on R-bloggers? click here if you have a blog, or here if you don't.