ruby - Why should I avoid using CGI? -


i trying create website using cgi , erb, when search on web, see people saying should avoid using cgi, , use rack.

i understand cgi fork lot of ruby processes, if use fastcgi, 1 persistent process created, , adopted php websites too. plus fastcgi interface create 1 object 1 request , has performance, opposed rack creates 7 objects @ once.

is there specific reason should not use cgi? or false assumption , entirely ok use cgi/fastcgi?

cgi, mean both interface , common programming libraries , practices around it, written in different time. has view of request handlers distinct processes connected webserver via environment variables , standard i/o streams.

this state-of-the-art in day, when there not "web frameworks" , "embedded server modules" think of them today. thus...

cgi tends slow

again, cgi model spawns 1 new process per connection. while spawning processes per se cheap these days, heavy web app initialization — reading , parsing scores of modules, making database connections, etc. — makes quite expensive.

cgi tends toward too-low-level (imho) design

again, cgi model explicitly mentions environment variables , standard input interface between request , handler. ... cares? that's lower level app designer should thinking about. if @ libraries , code based on cgi, you'll see bulk of encourages "business logic" right alongside form parsing , html generation, seen dangerous mixing of concerns.

contrast rack::builder, right away coder thinking of mapping namespace action, , means broader web application. (suddenly free argue semantic web , virtues of rest , , that, because we're not thinking generating radio buttons based off user-supplied input.)

yes, rack::builder implemented on top of cgi, but, that's point. it'd have layer of abstraction built on top of cgi.

cgi tends sneeringly dismissed

despite cgi working within limitations, despite being simple , understood, cgi dismissed out of hand. you, too, might dismissed out of hand if cgi know.


Comments

Post a Comment

Popular posts from this blog

Why does Ruby on Rails generate add a blank line to the end of a file? -

running rails generate controller foo home results in: class foocontroller < application controller def home end end (there's nothing on line in actual file, blank line) is there purpose blank line? it's common use newline indicate end of line, last line. many editors (like vi, use) add in newline silently. consensus text files (especially in unix world) should end in newline, , there have been problems historically if wasn't present. why should text files end newline? the tool used count lines in file "wc" counts newlines in file, without trailing newline show 3 instead of 4. it improves readability of templates used in generator. consider: https://github.com/rails/rails/blob/master/railties/lib/rails/generators/rails/controller/templates/controller.rb to remove trailing newline, template have last line of: end<% end -%> instead of: end <% end -%> that seems less readable me. the discussion below refers
Read more

keyboard - Smiles and long press feature in Android -

i've created android keyboard. how add features inserting smilies, , using long keypresses display symbols? to create long-press behavior allows select several options pop-up menu, follow guide (specifically pop-up menu section): http://developer.android.com/guide/topics/ui/menus.html smileys (also known emoticons) combination of keys, understood programs , parsed same way. have do, when clicks smiley face on keyboard, simulate pressing of key combination matching emoticon. example, when clicks smiley, should simulate key presses ':' , ')' :). here's list of emoticons: http://en.wikipedia.org/wiki/list_of_emoticons
Read more

node.js - Bad Request - node js ajax post -

i'm using express 3.0 , node v0.11.0. have button submits form , i'm using ajax post data json object node server. client code is: $('#contact').submit(function(e) { console.log('submit called'); var formdata = json.stringify($('form').serializeobject()); console.log(formdata); $.ajax({ url: "http://localhost:3000/savedata/", type: "post", datatype: 'json', data: {objectdata: formdata}, contenttype: "application/json", complete: function() { console.log('process complete'); }, success: function(data) { console.log('process sucess'); }, error: function() { console.log('process error'); }, }); return false; }); then on server: var express = require('express'); var app = express(); app.set('views', __dirname + '/views'); app.set('view engine', 'jade'); app.use(express.bodyparser());
Read more