kotovalexarian-likes-github/sinatra
1
0
Fork 0
mirror of https://github.com/sinatra/sinatra synced 2023-03-27 23:18:01 -04:00
Code Releases Activity

document modular vs. classic style, fixes #138

Browse source
This commit is contained in:
Konstantin Haase 2011-02-19 11:30:59 +01:00
parent 329747207f
commit 0152335d75
1 changed files with 27 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

27
README.rdoc
View file

@ -1224,6 +1224,33 @@ Sinatra::Base components with two modifications:
including the built-in server. See {Options and Configuration}[http://sinatra.github.com/configuration.html] including the built-in server. See {Options and Configuration}[http://sinatra.github.com/configuration.html]
for details on available options and their behavior. for details on available options and their behavior.
=== Modular vs. Classic Style
Contrary to common believes, there is nothing wrong with classic style. If it
suits your application, you do not have to switch to a modular application.
There are only two downsides compared to modulare style:
* You may only have one Sinatra application per Ruby process - if you plan to
use more, switch to modular style.
* Classic style pollutes Object with delegator methods - if you plan to ship
your application in a library/gem, switch to modular style.
There is no reason you cannot mix modular and classic style.
If switching from one style to the other, you should be aware of slight
differences in the setting:
Setting Classic Modular
app_file file loading sinatra nil
run $0 == app_file false
logging true false
method_override true false
inline_templates true false
=== Serving a Modular Application === Serving a Modular Application
There are two common options for starting a modular app, activly starting with There are two common options for starting a modular app, activly starting with